Additional Changes

Changes include versions and fixes based on testing and user feedback.

OSS Versions

See Third-Party Components for Storage 16.1.0 for the complete listing of packages and versions for this release.

Fixed in 16.1.0

• Fixed an issue where a node would fail to boot with one or more volume(s) with serious hardware failures. (SWAR-10051)

• Improved handling of frequent object locking updates on a single object. (SWAR-10046)

• Improved search feed recovery after Elasticsearch connection errors or other search cluster blockages. (SWAR-9970)

• Fixed a regression where EC conversion of obsolete versioned objects with ec.convertVersionedObjects=true was not recommended. Customers can resume use of this setting. (SWAR-10001)

• Fixed an issue in 16.0 where clusters with high data turnover and continuous defrgmentation would be subject to abnormal process growth during mount. (SWAR-10056)

• Swarm Storage 16.0 has a restriction where multipart upload requests that are partially completed on nodes running 15.x or earlier releases, do not complete successfully if these requests are continued or completed on Swarm 16.0. With 16.1 and later, the procedure Rolling Upgrades from Swarm 15.x to Swarm 16.x with Multipart Uploads allows upgrading without disrupting ongoing multipart uploads. (SWAR-10054)

Watch Items and Known Issues

The following watch items are known:

• Customizations to an Elasticsearch 6.8.6 /etc/elasticsearch/elasticsearch.yml path.data and network.host fields will be lost when running the configuration script to upgrade to Elasticsearch 7 if the upgrade does not complete. This can happen if the new Elasticsearch 7 rpm is not in the current directory and cannot be downloaded. Reapply your customizations as this will not affect upgrades starting with Elasticsearch 7.5.2. (SWAR-9977)

• Customers need to wait 1 min or more to get the changes done in feed definition to be effective throughout the cluster. (SWAR-10007)

• Swarm will attempt to determine if the volumes being used on a chassis are indeed separate devices. The serial number associated with each volume will be used for this determination. With default settings, Swarm will consider separate volumes on the same device as the same for protection purposes. EC segment placement may be impacted by this consideration. This behavior change will not impact most hardware-based clusters, but VM installations with virtual disks may need to lower the k value of their EC encoding to allow EC writes. (SWAR-10042)

These are standing operational limitations:

• The Storage UI shows no NFS config if the Elasticsearch cluster is wiped. Contact DataCore Support for help in repopulating the SwarmFS config information. (SWAR-8007)

• Any incomplete multipart upload into a bucket leaves the parts (unnamed streams) in the domain if the bucket is deleted. To find and delete those parts, use the s3cmd utility (search the Support site for "s3cmd" guidance). (SWAR-7690)

• The chassis shuts down but does not come back up when restarting a cluster of virtual machines that are UEFI-booted (versus legacy BIOS). (SWAR-8054)

• Invalid config parameters that prevent the unassigned nodes from booting are created if subcluster assignments are removed in the CSN UI. (SWAR-7675)

• Upgrading an elasticsearch 6.8.6 node using the configure script in caringo-elasticsearch-search-7.2.0 will fail with "ERROR: error parsing version". Please use caringo-elasticsearch-search-7.2.1 instead. (SWAR-10100)

• On node reboots, some feed statistics that are not persisted across boots may show up incorrectly. It will fix itself eventually. Currently, there is no workaround for this. (SWAR-9720)

To upgrade Swarm 9 or higher, proceed to How to Upgrade Swarm. For migration from Swarm 8.x or earlier, contact DataCore Support for guidance.

Deprecation

• The search.caseInsensitive is now deprecated and will be removed in a future release. (SWAR-10085)