...
Configuring elasticsearch.yml's network.host (https://www.elastic.co/guide/en/elasticsearch/reference/7.16/important-settings.html#network.host) to "__site__" might not choose the right IP to allow master election if the server is multi-homed. Modify the elasticsearch.yml to enter a specific IP for the node and the configuration script will preserve it. (SWAR-9350)
If you run into this issue, the fix is to:systemctl stop elasticsearch on all ES nodes
remove all the contents of the path.data directory
change network.host: <IP of ES NIC in the Storage VLAN>
systemctl start elasticsearch
Verify the configured “java.io.tmpdir” in “jvm.options” is writable to Elasticsearch for customers using Elasticsearch instances that fail to start with JNA warnings in Elasticsearch logs. Change “java.io.tmpdir” to
/var/log/elasticsearchas per desired security preferences. (SWAR-9347)Elasticsearch can fail to start and return a warning "unable to load JNA native support library", which is due to SELinux setting noexec “noexec” on
/tmp.
For Elasticsearch 7.5.2, edit “/etc/elasticsearch/jvm.optionsoptions” replacing the line "-Djava.io.tmpdir=${ES_TMPDIR}" with "-Djava.io.tmpdir=/var/log/elasticsearch". With Elasticsearch 7.17, uncomment the "Environment=ES_TMPDIR=/usr/share/elasticsearch/tmp" line in/etc/systemd/system/elasticsearch.service.d/override.confand create that directory. (SWAR-9347)Swarm versions 10.0 onward are vulnerable to kernel issues manifested on some Intel CPUs. Symptoms include lowered performance, long mount times, and cluster instability. Swarm versions 14.1 and later provide a workaround for this issue, see https://caringo.atlassian.net/wiki/spaces/KB/pages/2973204604. (SWAR-9055)
Customers who perform paginated listing queries (using sort and marker) need to choose a unique set of fields to return the complete results. (SWAR-9630)
...