| Table of Contents | ||
|---|---|---|
|
...
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)
...
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 drivedisk: The 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.forceLegacyNoncesettings from thenode.cfgfiles 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)
...
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
s3cmdutility (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 display during rolling reboot in versions 11.1 through 12.0.1. To mitigate this problem, set Set
scsp.forceLegacyNonce=Falsein the cluster configuration to mitigate this problem. 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)
...