...
| Excerpt |
|---|
Impacts for 11.3- Upgrading Elasticsearch — You may use Elasticsearch 5.6.12/2.3.3 with Storage 11 if you cannot move to ES 6 immediately, but start your migration now (see Migrating from Older Elasticsearch). Support for ES 5.6.12/2.3.3 will end in a future release, and testing for 2.3.3 with Swarm 11 is discontinued. Important: Always upgrade Swarm Search and Metrics at the same time that you upgrade ES. Do not run an ES 5 Search or Metrics Curator against ES 6.
- Rolling upgrade — During a rolling upgrade from a version older than 11.1, the mixed state in Swarm versions among nodes might cause errors in the Swarm UI (and in management API calls). Use the legacy Admin Console (port 90) to monitor the rolling upgrade. (SWAR-8716)
- Settings changes — The setting
health.parallelWriteTimeout, which was disabled by default, now defaults to 1 month. It sets when to time out an uncompleted multipart upload, triggering clean up of the unused parts. Do not disable (0) if using SwarmFS. (SWAR-8902) - Encryption-at-rest —If you are about to upgrade from Swarm 11.0 or earlier and you use encryption-at-rest, contact Support to ensure that you can smoothly roll back to your prior version, if needed. (SWAR-8941)
- Differences in
scsp.forceLegacyNonce configuration depending on the version you're upgrading from (SWAR-9020): If you are currently running a Swarm Storage version prior to 11.1, and upgrading to 11.1, 11.2, 11.3, 12.0 or 12.1: Before upgrading, set scsp.forceLegacyNonce=true in your node.cfg file. After the upgrade, when the cluster is fully up, update scsp.forceLegacyNonce=false using swarmctl and change scsp.forceLegacyNonce=false in your node.cfg file. If you are currently running a Swarm Storage version 11.1, 11.2, 11.3, 12.0 or 12.1 and upgrading to another version from that list: Before upgrading, verify that scsp.forceLegacyNonce=false is in your node.cfg file and verify using swarmctl that scsp.forceLegacyNonce=false in your cluster.
|
| Insert excerpt |
|---|
| Swarm Storage 11.2 Release |
|---|
| Swarm Storage 11.2 Release |
|---|
| nopanel | true |
|---|
|
...
- If you downgrade from Swarm 11.0, CRITICAL errors may appear on your feeds. To stop the errors, edit the existing feed definition names via the Swarm UI or legacy Admin Console. (SWAR-8543)
- 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 s3cmd utility (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)
- 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 Support so that your issue can be resolved. (SWAR-7556)
- If a feed is subject to a prolonged outage, a node reboot may be required for it to resume progress after the outage is cleared. If progress is not resolved after the reboot, contact Support. This has been resolved in 12.1.0 (SWAR-9062)
- If Elasticsearch 6.8.6 blocks an index due to low disk space, this will have to be issued against each index (
index_*, csmeter*, metrics*) in the read_only_allow_delete state. This is no longer an issue after upgrading to Swarm 12 / Elasticsearch 7 as it automatically unblocks when disk space frees up. (SWAR-8944)
curl -i -XPUT "<ESSERVERIP>:9200/<INDEXNAME>/_settings" -d '{"index.blocks.read_only_allow_delete" : null}' -H "Content-Type: application/json"
...
