...
...
...
...
...
...
Table of Contents | ||
---|---|---|
|
New Features
Erasure Coding Improvements — Swarm 14 includes Erasure Coding related improvements:
With Swarm 14.0 indexed erasure coded (EC) objects include the field "
ec_encoding
" which records the current EC coding of the object. Non-EC objects do not have this field. (SWAR-6653)Swarm now computes the data footprint of Erasure Coding EC segments and whole replicas objects separately during each HP cycle so the relative space usage of whole replicas vs EC can inform space usage policy decisions. (SWAR-9160)
Additional Changes
These items are other changes, including those that come from testing and user feedback.
OSS Versions — See Third-Party Components for Storage 14.0.1 for the complete listing of packages and versions for this release.
Fixed in 14.0
Reboot loop due to a bad drive: The Swarm node recognizes the volume as failed and alerts the cluster to the failure when a volume fails at mount time. The node operates with the remaining volumes, so physically removing the volume may be necessary. (SWAR-9189)
Remove legacy nonce handling: Remove
scsp.forceLegacyNonce
settings from thenode.cfg
files prior to upgrading to 14.0. (SWAR-9108)Bucket listings: During a node reboot, such as a rolling reboot of the cluster, a newly booted node temporarily returns an empty result set for a listing query. (SWAR-9083)
S3 backup feed: A 5G object size limitation has been removed. (SWAR-8554)
Upgrade Impacts
Info |
---|
RequiredComplete 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, Upgrading from Unsupported Elasticsearch. |
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.0
|
Info |
---|
Cumulative impactsAddress all upgrade impacts for each version released since the version being upgraded from. Review the comprehensive Upgrade Impacts listed for the Swarm Storage 14 Release. |
...
The following watch items are known:
A node fails to mount all disks in the node if a node mounts an encrypted volume that is missing the encryption key in the configuration. (SWAR-8762)
S3 Backup feeds do not yet backup logical objects larger than 5 GB; those writes fail with a
CRITICAL
log message. (SWAR-8554)The chassis shuts down but does not come back up when restarting a cluster of virtual machines that are UEFI-booted (versus legacy BIOS). (SWAR-8054)
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)
These are standing operational limitations:
The Storage UI shows no NFS config if the Elasticsearch cluster is wiped. Contact DataCore Support for help repopulating the SwarmFS config information. (SWAR-8007)
Any incomplete multipart upload into a bucket leaves the parts (unnamed streams) in the domain if a bucket is deleted. To find and delete them, use the
s3cmd
utility (search the Support site for "s3cmd
" for guidance). (SWAR-7690)Invalid config parameters that prevent the unassigned nodes from booting are created if subcluster assignments are removed in the CSN UI. (SWAR-7675)
False 404 Not Found and other SCSP errors may be seen during rolling reboot in versions 11.1 through 12.0.1. To mitigate this problem, set
scsp.forceLegacyNonce=False
in the cluster configuration. This setting needs to be removed before upgrading to 12.1.0 or later. (SWAR-9020)S3 Backup restoration to the cluster may be blocked if the certificate is not located where Swarm expects it when using certificates with HAProxy. From 12.1, a clearer error message draws attention to the issue for S3 backup and replication feeds that are blocked due to invalid X.509 ("SSL") certificates. (SWAR-8996)
To upgrade Swarm 9 or higher, proceed now to How to Upgrade Swarm. For migration from Swarm 8.x or earlier, contact DataCore Support for guidance.