Versions Compared

Old Version 10

changes.mady.by.user Anjali Tyagi

Saved on

compared with

New Version Current

changes.mady.by.user Bala Harish A(AC)

Saved on

Key

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

New Features

  • The DELETE operation returns the Castor-System-Delete-Marker-Etag header on a named or alias object in the versioning enabled or versioning suspended state. If versioning is disabled, the object is immutable or a context, and no such header is returned. The ETag of the delete marker (returned) is checked by INFO-ing the deleted object and checking the returned ETag header. (SWAR-9292)

  • Updated the DELETE behavior of the current object version that contains a non-deletion lifepoint. The behavior depends on the container's versioning state of an object and refers to the bucket for a named object. For alias tenanted objects, it is a domain's "unnamed" versioning policy. (SWAR-9265)

    • If the container is versioning disabled or versioning suspended, deletion of the current version fails, as before, with a 403.

    • If the container is versioning enabled, the delete succeeds and creates a delete marker, leaving the former current version as the first non-current version.

  • Swarm provides a setting (ec.convertToPolicy) to enable the conversion of existing EC objects to the current policy encoding. (SWAR-9203)

Additional Changes

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

OSS

...

Versions

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

Fixed in 14.1

  • Replication and S3

    backup feed

    Backup Feed: The feed is no longer reported as blocked for long-running replications (SWAR-9218). The object replication is allowed for custom metadata containing Non-ASCII characters. (SWAR-9212)

  • Bucket and

    domain renaming

    Domain Renaming: Swarm supports renaming of query arguments and bucket and domain using alias UUID. Renaming works with COPY, PUT, and APPEND operations, though COPY with the preserve query argument is advised. If a bucket or domain collision is detected, rename either context without colliding with each other. (SWAR-8708)

  • Bulk

    configuration

    Configuration: Swarm provides bulk Elasticsearch 7 nodes configuration to consistently use discovery.seed_hosts, not older discovery.zen settings. (SWARM-9395)

  • nicTable: It is populated again in SNMP; multiple new columns were added. (SWAR-9327)

  • SNMP

    certain communication stats

    Certain Communication Stats:Swarm now publishes via SNMP communication stats summarized over a moving window covering the last hour. A new daily stats table in SNMP publishes both communication and network interface stats summarized over a moving window covering the last day. The daily stats are updated every hour. (SWAR-8124)

  • Large

    physical memory support

    Physical Memory Support: The EFQ02 errors are not received in logs while running the 14.1 release on nodes with large physical memory (>116G). (SWAR-9353)

  • NTP

    dependency

    Dependency: NTP dependency checks are improved for configured time servers that either fail to respond quickly or respond using an older NTP version. (SWAR-9373)

  • USB Booting: Swarm 14.1.1 now supports booting from a USB drive. This was not working in 14.1.0. (SWAR-9419)

  • Replication

    failing

    Failing on

    gems cluster

    Gems Cluster: Remote replication feed cannot replicate some objects in the versioned buckets in Swarm 14.1.2. (SWAR-9428)

Upgrade Impacts

Info

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

Impacts for 14.1

  • 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 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 run the following cURL to clear the space in the Elasticsearch cluster. (SWAR-8982)

    Code Block
    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 settingsUse 
Check or Change Settings
  1. Check the value of scsp.forceLegacyNonce using below command:
    'swarmctl -C scsp.forceLegacyNonce'
 to check 
  2. Set the value 
 of scsp.
  1. to False.
forceLegacyNonce

Use 
  1. 'swarmctl -C scsp.forceLegacyNonce -V False'
 to set the value to false.For more details, see 
See https://support.cloud.caringo.com/tools/Tech-Support-Scripts-Bundle-swarmctl.pdf for more details.
 Info
Cumulative 
 impacts
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:
...
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.
 Note
Caution
Multipath Support is obsolete from Swarm 10 onward.