Additional Changes

Changes include versions and fixes coming from testing and user feedback:

OSS Versions

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

Fixed in 15.1

• Better Retiring Rate: Improved the retiring rate of volume in some cases. (SWAR-9579)

• Updated Swarm Error Report: The body message of the SCSP error is updated. Now, the term "CAStor error" has been replaced with "Swarm Storage error" in the error message. (SWAR-9563)

• Removed Archive Mode: Archive mode feature has been removed from v15.1. (SWAR-9528)

• Recursive Bucket Deletion: Fixed an issue where the health processor cannot reclaim obsolete object versions during recursive delete reclaimation. (SWAR-9582)

• Feed Overlapping: The feed overlap error is fixed in v15.1 which prevents the addition of a feed in both the UI and port 90 consoles. (SWAR-9601)

• 507 Error Response: Fixed the write requests under the high loads, which were occasionally failing with 507 error responses. (SWAR-9596)

• Search Feed: Fixed the creation of a new search feed with a feed id less than the default search feed that results in the new feed becoming the default. (SWAR-9572)

• Elasticsearch Record for Missing Object: Sometimes, the failed write requests created an Elasticsearch record for missing objects (objects that were not created), which has been fixed in v15.1. Fixed an issue where, in rare cases, failed policy-related requests would result in lost object versions. (SWAR-9607)

Watch Items and Known Issues

The following watch items are known:

• Configuring elasticsearch.yml's network.host (https://www.elastic.co/guide/en/elasticsearch/reference/7.16/important-settings.html#network.host) to "__site__" might not choose the right IP to allow master election if the server is multi-homed. Modify the elasticsearch.yml to enter a specific IP for the node and the configuration script will preserve it. (SWAR-9350)
  If you run into this issue, the fix is to:

  • systemctl stop elasticsearch on all ES nodes

  • remove all the contents of the path.data directory

  • change network.host: <IP of ES NIC in the Storage VLAN>

  • systemctl start elasticsearch

• Verify the configured “java.io.tmpdir” in “jvm.options” is writable to Elasticsearch for customers using Elasticsearch instances that fail to start with JNA warnings in Elasticsearch logs. Change “java.io.tmpdir” to /var/log/elasticsearch as per desired security preferences. (SWAR-9347)

• Swarm versions 10.0 onward are vulnerable to kernel issues manifested on some Intel CPUs. Symptoms include lowered performance, long mount times, and cluster instability. Swarm versions 14.1 and later provide a workaround for this issue, see https://caringo.atlassian.net/wiki/spaces/KB/pages/2973204604. (SWAR-9055)

• Customers who perform paginated listing queries (using sort and marker) need to choose a unique set of fields to return the complete results. (SWAR-9630)

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 a 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)

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