| Table of Contents | ||
|---|---|---|
|
...
Erasure Coding Improvements — Swarm 14 includes Erasure Coding related improvements:
- With Swarm 14.0 erasure coded (EC) objects that are indexed will include the field "
ec_encoding" that gives the current EC coding of the object. Non-EC objects will 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 that the relative space usage of whole replicas vs EC can inform space usage policy decisions. (SWAR-9160)
...
| Info | ||
|---|---|---|
| ||
| If you are on older Elasticsearch (5.6.12 or 2.3.3), complete your migration to Swarm 11.3 and ES 6.8.6 before upgrading to Swarm 14. See /wiki/spaces/GRAV/pages/2246995118See here, Upgrading from Unsupported Elasticsearch. |
...
| Info | ||
|---|---|---|
| ||
Be sure to address all of the upgrade impacts for each version released since the version you are now upgrading. Review the comprehensive Upgrade Impacts listed for the Swarm Storage 14 Release. |
Watch Items and Known Issues
...
- If you wipe your Elasticsearch cluster, the Storage UI will show no NFS config. Contact 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
s3cmdutility (search the Support site for "s3cmd" for guidance). (SWAR-7690) - If you remove subcluster assignments in the CSN UI, doing so creates invalid config parameters that will prevent the unassigned nodes from booting. (SWAR-7675)
- You may see false 404 Not Found and other SCSP errors during rolling reboot in versions 11.1 through 12.0.1. To mitigate this problem, set
scsp.forceLegacyNonce=Falsein the cluster configuration. You will need to remove this setting before upgrading to 12.1.0 or later. (SWAR-9020) - When you use certificates with HAProxy, S3 Backup restoration to the cluster may be blocked if the certificate is not located where Swarm expects it. 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)
...