...

• Default PDI Enablement: Per Domain Indexing (PDI) is enabled by default. (SWAR-10359)

• ES8 Support: Swarm supports Elasticsearch (ES) 8 and later, starting from Storage 17.0. (SWAR-9536)

• Search Feed Deletion Improvement: Deleting a Search Feed created with search.perDomainIndex=True now removes all associated domain indices in Elasticsearch. Use the Storage UI for this, not the legacy port 90 console. (SWAR-10264)

• Uninitialized / Used disks: To prevent potential data loss when hot-plugging partitioned, used, or unformatted disks/volumes, DataCore recommends checking and formatting the disk before attaching it to a Swarm Storage Node. (SWAR-10206)

• Memory Leak Fix: Fixed memory leak issue which occurred over time in the loaded cluster. (SWAR-10124)

• Node Reboot During Heavy Load: Fixed an issue that caused Swarm Storage Nodes to reboot under heavy load due to SCSP process failures. (SWAR-10319)

• Recovery Failure: Fixed an issue where volumes pending for mount were added to the recovery suspend list, causing no recovery. (SWAR-10061)

• New Setting (disk.enforceEmergencyDefrag): Added disk.enforceEmergencyDefrag setting to enable high-priority defragmentation without additional configurations. (SWAR-9276)

• SSD Trim Support: Storage nodes support SAS and SATA-based SSDs, starting from Storage 17.0. (SWAR-9883)

• New Setting (node.maxRPCPollsLost): Resolved Swarm node reboots under load by introducing node.maxRPCPollsLost to throttle on RPC status loss. (SWAR-10319)

• New API Schema fields: Added new API schema fields (usedMBytes, trappedMBytes, and usedSpaceMB) from Storage 17.0.

• 409 Error Due to Full Volumes: Swarm keeps trying to use full volumes and occasionally the retry fails with a 409 error under heavy load scenarios. (SWAR-10249)

• CIP Settings Update: Verify cip.processes = 2, update the setting cip.readRetries=7, cip.deleteRetries=7, and cip.replicastRetries=7 to mitigate the false 404s error that occurs sometimes in Swarm responses during heavy load situations. (SWAR-10120)

Watch Items and Known Issues

...

• Customizations to an Elasticsearch 6.8.6 /etc/elasticsearch/elasticsearch.yml path.data and network.host fields will be lost when running the configuration script to upgrade to Elasticsearch 7 if the upgrade is incomplete. This can happen if the new Elasticsearch 7 rpm is not in the current directory and cannot be downloaded. Reapply your customizations as this will not affect upgrades starting with Elasticsearch 7.5.2. Users need to back up their customizations before running the upgrade script. (SWAR-9977)False 404s might be seen in the Swarm responses during heavy load situations. To mitigate this, verify cip.processes = 2. Also update the settings for cip.readRetries=7, cip.deleteRetries=7, cip.replicastRetries=7. (SWAR-10120)

• When using search.perDomainIndex=True (under Support guidance), the number of supported domains is limited based on the number of data nodes in the Elasticsearch cluster and search.numberOfShards. For example, five data nodes support 5x600 shards at search.numberOfShards=5; each domain requires 5x2 (primary and replica) shards. Also remember Gateway creates daily csmeter indices, 1 shard x 2 each, for 100 days (retentionDays) plus a csmeterlock index. So the maximum number of domains supported is about 275. After that new domain indices cannot be created resulting in a domain listing returning a 503 ReaderUnavailableIndex. The castor.log will show errors EFD19, EIP15, and EIP02.
  For example, "Validation Failed: this action would add [6] shards, but the cluster currently has maximum [999]/[1000] normal open shards". Error reporting will be improved in a future release. (SWAR-10172)

...