...
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, please verify cip.processes = 2, and keep increasing the cip.queryMinimumTimeout value gradually until the 404 occurrences are reduced. 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)
...