Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

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

    • Replication failing on gems cluster — Remote replication feed cannot replicate objects in the versioned buckets.

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:

Excerpt
nameImpacts for 14.1.2

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 Grafana and Prometheus Node Exporter. 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.

Info

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.

Info

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:

...