...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

New Features

Expanded SEND — : SCSP SEND, an admin-only method that allows forcing an object to be written immediately in another cluster, now works with every type of and any number of Swarm feeds: replication, search, and S3 backup. The expanded functionality works through several new query arguments, two to specify which feed IDs or types to target and one to control the timeout (if any) for the request to complete. See SCSP SEND. (SWAR-8441)

Elasticsearch — : This release focuses on changes that make it easier to monitor and manage Elasticsearch, Swarm Search, and Swarm Metrics:

• The Swarm Search RPM installation now checks and warns if firewalld is enabled, reminding

  you

  to check the firewall rules for ports 9200 and 9300, which are needed by Elasticsearch. (SWAR-8416) 

• Swarm dynamically updates DNS lookups after Elasticsearch nodes are restarted. (SWAR-8817)

• The

  Swarm Metrics

  Swarm Metrics curator is now independent of HTTP_PROXY and related shell environment variables and so is less subject to disruption. (SWAR-8452)

• The

  Swarm Metrics

  Swarm Metrics curator has improved defaults for its logging, increased to 10 logs and up to 10 MB. (SWAR-8401)

This release also includes changes to help with Swarm management and performance:

• Swarm now ships with the Prometheus Node Exporter enabled and configured to work by default, to simplify implementation and avoid rebooting. To disable the Node Exporter on a node, set "metrics.enabledNodeExporter=False" in the node's configuration file; to disable across the entire cluster, set metrics.nodeExporterFrequency to 0. (SWAR-8578)

• Swarm's inter-process locking process has been reworked, granting a small performance gain for larger clusters and a reduction in related WARNING-level log messages. (SWAR-8835)

• Swarm has restored performance for clients who have not

  yet

  migrated from legacy authentication/authorization. (SWAR-8810) 

Additional Changes

These items are other changes, including those that come from testing and user feedback.

OSS

...

Versions

See Third-Party Components for 11.2

...

for the complete listing of packages and versions.

Fixed in 11.2.0

• The multipart write 202 response now includes Location headers of the resulting manifests that are analogous to the Location headers of a normal EC write. (SWAR-8886)

• Resolved an error in the assessment of licensed space usage that prevented a node from accepting writes. (SWAR-8869)

• Resolved an issue related to TCP window sizes that can cause socket disconnects, pauses, and hangs. (SWAR-8847)

• Resolved an issue that can lead to a node crash in large clusters. (SWAR-8832)

• Basic auth of the admin user for special administrative SCSP requests did not correctly handle a stored hashed admin password

...

• . (SWAR-8814)

• Infrequent WARNING messages, "Node/Volume entry not published due to lock contention (...); action will be retried,"

...

• may appear in logs. (SWAR-8802)

• Resolved an issue

...

• causing rebooted Swarm nodes to allow client requests before mounting all

...

• volumes. (SWAR-8801)

Upgrade Impacts

Be sure to use Use the supported versions of Swarm components for your the target version of Elasticsearch:

These items are changes to the product function that may require operational or development changes for integrated applications. Address  Address the upgrade impacts for each of the versions since the one you are currently running version:

Watch Items and Known Issues

The following operational limitations and watch items exist in this release.

• If a node mounts an encrypted volume that is missing the encryption key in the configuration, the node

  will fail

  fails to mount all

  of the

  disks in the node. (SWAR-8762)

• S3 Backup feeds do not

  yet

  backup logical objects

  larger

  greater than 5 GB. (SWAR-8554)

• If

  you downgrade

  downgrading from Swarm 11.0, CRITICAL errors may appear on

  your

  the feeds. To stop the errors, edit the existing feed definition names via the Swarm UI or legacy Admin Console. (SWAR-8543)

• When restarting a cluster of virtual machines that are UEFI-booted (versus legacy BIOS), the chassis shut down but do not come back up. (SWAR-8054)

• If

  you wipe your

  wiping the Elasticsearch cluster, the Storage UI

  will show

  shows no NFS config. Contact DataCore Support for help repopulating

  your

  the SwarmFS config information. (SWAR-8007)

• If

  you delete a

  bucket is deleted, any incomplete multipart upload into that bucket

  will leave its

  leaves the parts (unnamed streams) in the domain. To find and delete them, use the s3cmd utility (search the Support site for "s3cmd" for guidance). (SWAR-7690)

• Logs showed the error "FEEDS WARNING: calcFeedInfo(etag=xxx) cannot find domain xxx, which is needed for a domains-specific replication feed". The root cause is fixed; if

  you received

  such warnings are received, contact DataCore Support so

  that your

  the issue can be resolved. (SWAR-7556

  )With multipath-enabled hardware, the Swarm console Disk Volume Menu may erroneously show too many disks, having multiplied the actual disks in use by the number of possible paths to them. (SWAR-7248

  )

Note these installation issues:

• The elasticsearch-curator package may show an error during an upgrade, which is a known curator issue. Workaround: Reinstall the curator: yum reinstall elasticsearch-curator (SWAR-7439)

• Do not install the Swarm Search RPM before installing Java. If Gateway startup fails with "Caringo script plugin is missing from indexer nodes", uninstall and reinstall the Swarm Search RPM. (SWAR-7688)

Upgrading Swarm

To Proceed to How to Upgrade Swarm to upgrade Swarm 9 or higher, proceed to How to Upgrade Swarm.