Page Comparison

...

• Swarm 10 Performance — With Storage 10.1, the performance both for writes and for erasure-coded object reads is improved for Swarm 10's density-friendly single-IP architecture, the result of optimizations in how Swarm nodes write to volumes under the new design. (SWAR-8357) 

• Memory Handling — Swarm has improved memory handling, especially with bursts and high loads, and 503 Service Unavailable responses are less likely. (SWAR-8335)

• Hardware Diagnostics — This release includes a preview of the Prometheus Node Exporter, for monitoring and diagnostics on the machines in the Swarm cluster. Prometheus is an open-source systems monitoring and alerting toolkit. It allows viewing of statistics available for the system, even under failure conditions. Prometheus scrapes metrics from instrumented jobs, running rules over this data to record aggregated time series or to generate alerts. Grafana and other API consumers can allow visualizing the collected data. The new setting  metrics.enableNodeExporter enables Swarm to run the Prometheus node exporter on port 9100. As a preview, the settings and implementation are subject to change; for more about this preview, contract DataCore Support. (SWAR-8170)

• Bulk Reformatting — Retiring volumes in order to implement encryption at rest requires you to then reformat and remount the volumes. Contact DataCore Support for a utility to streamline this process. (SWAR-8088)

• ES Cluster Configuration — The automation script for configuring Elasticsearch for Swarm generates the complete set of unique configuration files for each node in the Elasticsearch cluster. (SWAR-8028)

...

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

• The rate at which nodes retire is slower in Swarm 10.x than 9.6. (SWAR-8386)

• When restarting a cluster of UEFI-booted (versus legacy BIOS) virtual machines, 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. Contract DataCore Support for help repopulating your SwarmFS config information. (SWAR-8007)

• If you delete a bucket, any incomplete multipart upload into the bucket leaves the 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)

• Dell DX hardware will have less chassis-level monitoring information available via SNMP. If this is a concern, contract DataCore Support. (SWAR-7606)

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

...

1. Download the correct bundle for your site. Swarm distributions bundle together the core components needed for implementation and later updates; the latest versions are available in the Downloads section on the DataCore Support Portal. 
   Two bundles are available:

   • Platform CSN 8.3 Full Install or Update (for CSN environments) — Flat structure for scripted install/update on a CSN (see CSN Upgrades).

   • Swarm 10 Software Bundle (Platform 9.x and custom environments) — Contains complete updates of all core components, organized hierarchically by component.

2. Download the comprehensive PDF of Swarm Documentation matching the bundle distribution date, or use the online HTML version from the Documentation Archive.

3. Choose the type of upgrade. Swarm supports rolling upgrades (a single cluster running mixed versions during the upgrade process) and requires no data conversion unless noted for a release. Upgrades can be performed without scheduling an outage or bringing down the cluster. Restart the nodes one at a time with the new version and the cluster continues serving applications during the upgrade process.

   • Rolling upgrade: Reboot one node at a time and wait for its status to show as "OK" in the UI before rebooting the next node.

   • Alternative: Reboot the entire cluster at once after the software on all USB flash drives or the centralized configuration location has been updated.

4. Choose whether to upgrade Elasticsearch 2.3.3 at this time. 

   • To upgrade to Elasticsearch 5.6 with an existing cluster, reindex Search data and migrate any Metrics data to be kept. See Migrating from Older Elasticsearch for details. (SWAR-7395) 

5. Note these installation issues:

   • The elasticsearch-curator package may show an error during an upgrade, which is a known curator issue. Workaround: Reinstall the curator: yum reinstall elasticsearch-curator (SWAR-7439)

   • Do not install the Swarm Search RPM before installing Java. If Gateway startup fails with "Caringo script plugin is missing from indexer nodes", uninstall and reinstall the Swarm Search RPM. (SWAR-7688)

   • During a rolling upgrade from 9.0.x–9.2.x, you may see intermittent "WriterMissingRemoteMD5 error token" errors from a client write operation through the Gateway or on writes with gencontentmd5 (or the equivalent). To prevent this, set autoRepOnWrite=0 during the upgrade and restore autoRepOnWrite=1 after it completes. (SWAR-7756)

6. Review the Application and Configuration Guidance.