Page Comparison

...

Table of Contents

maxLevel	2

New Features

Swarm 10 Performance — With Storage 10.1, the
performance both
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
your
the Swarm cluster. Prometheus
is
is an open-source systems monitoring and alerting toolkit
that lets you view what statistics are
. It allows viewing of statistics available for
your
the system, even under failure conditions.
Prometheus
Prometheus scrapes metrics from instrumented jobs, running rules over this data to record aggregated time series or to generate alerts. Grafana
and
and other API consumers can
let you visualize
allow visualizing the collected data. The new
setting
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, contact DataCore Support. (SWAR-8170)
Bulk Reformatting — Retiring volumes
in order
to implement encryption at rest requires
you to then reformat and remount
reformatting and remounting the volumes.
You can now contact
Contact DataCore Support for a utility to streamline this process. (SWAR-8088)
ES Cluster Configuration — The automation script for configuring Elasticsearch for Swarm
now
generates the complete set of unique configuration files for each node in the Elasticsearch cluster. (SWAR-8028)

Additional Changes

These items are other changes and improvements including those that come from testing and user feedback.

OSS Updates — Storage 10.0 includes updates to third-party components. See Third-Party Components for 10.0 for the complete listing of packages and versions.
SCSP Errors — Several new error tokens and error improvements

...

are added for this release. See Error Response Headers.
Blocked Feeds
- Swarm can now detect the disappearance of the Elasticsearch index associated with a feed and mark the feed as Blocked; such feeds may need to be deleted and recreated. (SWAR-6885)
- Blocked feeds are retried every 20 minutes, but changing the definition for a blocked feed now triggers an immediate attempt with the new definition, which

...

- may clear the blockage. (SWAR-8232)
- The handling and reporting of feeds

...

- blocked due to internal software issues

...

- is improved. (SWAR-8267)
Fixed
- The correct behavior for the network.ntpControlKey setting was restored. (SWAR-8371)
- After an upgrade to version 10.0, the Chassis Details in the Swarm UI did not update the node listings correctly for a period of time. (SWAR-8352)
- When SwarmFS was not in use, clicking on the NFS settings link in the Storage UI resulted in an error. (SWAR-8350)
- The correct behavior for the

...

- disk light toggle in the Swarm UI

...

- is restored. (SWAR-8336)
- The SNMP MIB entries for the largest stream (volLargestStreamMB and volLargestStreamUUID)

...

- are not

...

- populated. (SWAR-8331)
- Rapid updates of objects written with replicate=immediate

...

- may result in some replicas not being found temporarily. (SWAR-8249)
- Deletes of unnamed objects did not update the Elasticsearch index, leaving a stale entry. (SWAR-8218)
- Deletes

...

- not processed by a feed within two weeks

...

- are not propagated to the feed's destination (Elasticsearch or the replication target). (SWAR-7950)

Upgrade Impacts

These items are changes to the product function that may require requiring operational or development changes for integrated applications.

Excerpt

Impacts for 10.1

Upgrading Elasticsearch —
You may continue
Continue to use Elasticsearch 2.3.3 with Storage 10.1 until
you are
able to move to 5.6 (see Migrating from Older Elasticsearch). Support for ES 2.3.3
will end
ends in a future release.
Before you upgrade to Gateway 6.0, however, you must complete
Complete the upgrade to Elasticsearch 5.6 before upgrading to Gateway 6.0.
Configuration Settings
— Be sure to run
— Run the Storage Settings Checker before any Swarm 10 upgrade to identify configuration issues.
- metrics.enableNodeExporter=true enables Swarm to run the Prometheus node exporter on port 9100. (SWAR-8170)
IP address update delay — When upgrading from Swarm 9 to the new architecture of Swarm 10, note
that
the "ghosts" of previously used IP addresses
might
may appear in the Storage UI; these
will
resolve within 4 days. (SWAR-8351)
Update MIBs on CSN
—
— Before upgrading to Storage 10.x, the MIBs on the CSN must be updated. From the Swarm Support tools bundle, run the platform-update-mibs.sh script. (CSN-1872)

Insert excerpt

	Swarm Storage 10.0 Release
	Swarm Storage 10.0 Release
nopanel	true

For Swarm 9 impacts, see Swarm Storage 9 Releases.

...

The following operational limitations and watch items exist in this release.

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)
The rate at which nodes retire is slower in Swarm 10.x than 9.6. (SWAR-8386)
When restarting a cluster of
virtual machines that are
UEFI-booted (versus legacy BIOS) virtual machines, the chassis shut down but do not come back up. (SWAR-8054)
If
you wipe your
the Elasticsearch cluster is wiped, the Storage UI
will show
shows no NFS config.
Contact
Contract DataCore Support for help repopulating
your
the SwarmFS config information. (SWAR-8007)
If
you delete
a bucket is deleted, any incomplete multipart upload into
that bucket will leave its
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
has less chassis-level monitoring information available
via
using SNMP. If this is a concern,
contact
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 are received, contact DataCore Support so
that your
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)

Upgrading from 9.x

Info

title

Important

Do not begin the upgrade until you complete the following are completed:

Plan upgrade impacts — Review and plan for this release's upgrade impacts (above) and the impacts for each of the releases since the running version
you are running
. For Swarm 9 impacts, see Swarm Storage 9 Releases.
Finish volume retires — Do not start any elective volume retirements during the upgrade. Wait until the upgrade is complete before initiating any retires.
Run checker script — Swarm 10 includes a migration checker script to run before upgrading from Swarm 9; it reports configuration setting issues and deprecations
that must
to be addressed. (SWAR-8230) See Storage Settings Checker.

If you need to upgrade upgrading from Swarm 8.x or earlier, contact DataCore Support for guidance.

Download the correct bundle for
your
the site. Swarm distributions bundle together the core components
that you need
needed for
both
implementation and later updates; the latest versions are available in
the
the Downloads section
on the
on the DataCore Support Portal.
There
Two bundles are
two bundles
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.
  InfotitleNote
  Contact Support for new installs of Platform Server and for optional Swarm client components, such as SwarmFS Implementation, that have separate distributions.
Download the comprehensive PDF of Swarm Documentation
that matches your
matching the bundle distribution date, or use the online HTML version from
the
the Documentation Archive.
Choose
your
the type of upgrade. Swarm supports rolling upgrades (a single cluster running mixed versions during the upgrade process) and requires no data conversion unless
specifically
noted for a
particular
release.
This means that you can upgrade
Upgrades can be performed without scheduling an outage or bringing down the cluster.
Just restart your
Restart the nodes one at a time with the new version and the cluster
will continue
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
  is updated.
Choose whether to upgrade Elasticsearch 2.3.3 at this time.
- To upgrade to Elasticsearch 5.6 with an existing cluster,
  you must
  reindex
  your
  Search data and migrate any Metrics data
  that you want
  to
  keep
  be kept. See Migrating from Older Elasticsearch for details. (SWAR-7395)
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: (SWAR-7439)
  Code Block
  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 may be seen 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)
Review the Application and Configuration Guidance.

Info

Note

Contact DataCore Support for new installs of Platform Server and for optional Swarm client components, such as SwarmFS Implementation, with separate distributions.

Versions Compared

Old Version 4

New Version Current

Key