Versions Compared

Old Version 4

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version 5

changes.mady.by.user Kyle Miller

Saved on

Key

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

...

  • Swarm 10 Performance 

    • The rate at which nodes retire is now improved over both version 10.1 and version 9.6 of Swarm Storage. (SWAR-8386)

    • Swarm has boosted the performance of erasure-coded range reads under high loads. (SWAR-8182)

  • Prometheus Node Exporter — The Prometheus Node Exporter preview has configuration enhancements.

    • The service is now enabled by default (metrics.enableNodeExporter=True), which makes basic hardware queries across nodes available without reboot.

    • A new setting, metrics.nodeExporterFrequency, sets how frequently to refresh Swarm-specific metrics in Elasticsearch; it defaults to 0, which disables this export. (SWAR-8408)

  • Swarm Management  

    • The new node-level Swarm configuration setting security.securePhysicalConsole lets you lock allows locking out access to the console's System Menu commands. This security measure is for nodes that are located where they could be at risk for unauthorized viewing and tampering. (10.2.1: SWAR-5309)

    • To ease upgrades to Swarm 10, the cluster-wide setting ec.protectionLevel is now a persisted setting, so that it can be changed on demand via Swarm UI or SNMP. The setting is no longer managed within and across config files, requiring consistency and cluster restarts. (SWAR-8231)

    • For better management of multipart uploads, both castor-system-uploadid and castor-system-partnumber now allow query args to use either hyphens or underscores in the field name, as is supported for metadata headers such as content-type. (SWAR-8274)

    • Swarm now raises alerts on objects that have persistent feed-related failures, such as objects that cannot be indexed in Elasticsearch or be remotely replicated. To investigate the cause for such failures, examine the details in the logs. (SWAR-8383)

    • The versions query argument on listing queries now accepts versions=previous to limit results to only the past versions of an object. (SWAR-6847)

    • Swarm now accepts named objects whose path name relative to the bucket looks like a UUID (32-character hexadecimal). (SWAR-8199)

...

Excerpt

Impacts for 10.2

  • Upgrading Elasticsearch — You may continue to use Elasticsearch 2.3.3 with Storage 10.2 until you are able to move to 5.6 (see Migrating from Older Elasticsearch). Support for ES 2.3.3 will end in a future release. Before you upgrade to Gateway 6.0, however, you must complete the upgrade to Elasticsearch 5.6.

  • Configuration Settings — Be sure to run the Storage Settings Checker before any Swarm 10 upgrade to identify configuration issues. Note these changes:

    • ec.protectionLevel is now persisted. (SWAR-8231)

    • index.ovMinNodes=3 is the new default for the overlay index, in support of Swarm 10's new architecture. To keep your overlay index operational, set this new value in your cluster, through the UI or by SNMP (overlayMinNodes). (SWAR-8278)

    • metrics.enableNodeExporter can be set to True, which enables the Prometheus Node Exporter on that node. (SWAR-8408, SWAR-8578)

    • metrics.nodeExporterFrequency, a new dynamic setting, sets how frequently to refresh Swarm-specific Prometheus metrics in Elasticsearch; it defaults to 0, which disables this export. (SWAR-8408).

...

  • Under some conditions, Swarm might start without mounting some of its volumes. If this happens, reboot the node. (10.2.1: SWAR-8597)

  • The OS in 10.2.1 cannot mount USB flash drives and so cannot read node.cfg files from them. If you boot Swarm from a USB drive, contact DataCore Support for a corrected version. (10.2.1: SWAR-8501)

  • During a rolling reboot of a small cluster, erroneous CRITICAL errors may appear on the console, claiming that EC objects have insufficient protection. These errors may be disregarded. (SWAR-8421)

  • When restarting a cluster of virtual machines that are UEFI-booted (versus legacy BIOS), the chassis shut down but do not come back up. (SWAR-8054)

  • If you wipe your Elasticsearch cluster, the Storage UI will show no NFS config. Contact DataCore Support for help repopulating your SwarmFS config information. (SWAR-8007)

  • If you delete a bucket, any incomplete multipart upload into that bucket will leave its parts (unnamed streams) in the domain. To find and delete them, use the s3cmd utility (search the Support site for "s3cmd" for guidance). (SWAR-7690)

  • Logs showed the error "FEEDS WARNING: calcFeedInfo(etag=xxx) couldn't find domain xxx, which is needed for a domains-specific replication feed". The root cause is fixed; if you received such warnings, contact DataCore Support so the issue can be resolved. (SWAR-7556)

  • With multipath-enabled hardware, the Swarm console Disk Volume Menu may erroneously show too many disks, having multiplied the actual disks in use by the number of possible paths to them. (SWAR-7248)

...