Swarm Storage 14.1.2 Release

Owned by Anjali Tyagi
Last updated: Feb 02, 2024 by Bala Harish A(AC)
3 min read

Additional Changes

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

OSS Versions

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

Fixed in 14.1.2

  • Variant Remote Replication Failure: Remote replication feed cannot replicate objects in the versioned buckets. (SWAR-9428)

Upgrade Impacts

Required

Complete the migration to Swarm 11.3 and ES 6.8.6 before upgrading to Swarm 14 if running older Elasticsearch (5.6.12 or 2.3.3). See here for upgrading from an unsupported Elasticsearch version.

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

Impacts for 14.1.2

  • Swarm storage node metrics are deprecated and are replaced in the next major release by the graphs and reporting from Prometheus Node Exporter and Grafana. The storage administration UI is updated to allow for metrics to be turned off. Clear metrics.target from the configuration, uninstall caringo-elasticsearch-metrics, and curl -XDELETE 'http://ELASTICSEARCH:9200/metrics-*' to clear the space in the Elasticsearch cluster. (SWAR-8982)

  • Differences in scsp.forceLegacyNonce configuration depends on the version upgrading from. (SWAR-9020)

    • Currently running a Swarm Storage version prior to 11.1, and upgrading to 11.1, 11.2, 11.3, 12.0 or 12.1:

      Before upgrading, set scsp.forceLegacyNonce=true in the node.cfg file. After the upgrade, when the cluster is fully up, update scsp.forceLegacyNonce=false using swarmctl and change scsp.forceLegacyNonce=false in the node.cfg file.

    • Currently running a Swarm Storage version 11.1, 11.2, 11.3, 12.0 or 12.1 and upgrading to another version from that list:

      Before upgrading, verify scsp.forceLegacyNonce=false is in the node.cfg file using swarmctl that scsp.forceLegacyNonce=false is in a cluster.

    • Currently running a Swarm storage version 11.1, 11.2, 11.3, 12.1 or 14.0 and upgrading to 14.1 or later:
      Remove scsp.forceLegacyNoncefrom the node.cfg file.

Use swarmctl to Check or Change Settings

Use 'swarmctl -C scsp.forceLegacyNonce' to check the value of scsp.forceLegacyNonce.

Use 'swarmctl -C scsp.forceLegacyNonce -V False' to set the value to false.

For more details, see https://support.cloud.datacore.com/tools/Tech-Support-Scripts-Bundle-swarmctl.pdf.

Cumulative Impacts

Address all upgrade impacts for each version released since the version being upgraded from.

Watch Items and Known Issues

The following watch items are known:

  • A node fails to mount all disks in the node if the node mounts an encrypted volume with a missing encryption key in the configuration. (SWAR-8762)

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

  • Lifecycle policy NamePrefix rules (for Non-ASCII characters) do not match the intended objects, hence, the rule does not fire. (SWAR-9413)

  • Dates used in lifecycle policy rules do not include a time specifier or time zone specifier. Use YYYY-MM-DD or YYYMMDD formatted dates only. This restriction will be relaxed in later releases. (SWAR-9408)

  • 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 a kernel issue manifested on some Intel CPUs. Symptoms include lowered performance, long mount times, and cluster instability. Swarm 14.1 provides a work-around for this issue, see Intel Skylake/Cascade Lake CPU Performance Issue). (SWAR-9055)

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)

  • 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 How to Upgrade Swarm. For migration from Swarm 8.x or earlier, contact DataCore Support for guidance.

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.