...
The jvm.options workaround works with 7.5.2, 6.8.6 and 5.6.12.
Elasticsearch 6.8.6 and 7.5.2 bundle bundles its own Java, they , recent, Java. It does not use the OS package “java-openjdk-1.8.0” so that package can be removed from elasticsearch 7.5.2 servers. The unsupported elasticsearch . Elasticsearch 6.8.6 and 5.6.12 does do use the OS java, so it’s good to update it.
This workaround is unnecessary with the unsupported elasticsearch 2.3.3 since it does not use log4j2.
Recent elasticsearch documentation mentions a
/etc/elasticsearch/jvm.options.d/directory can be used. But the elasticsearch 6.8.6 and 7.5.2 that Swarm supports will not use that directory, so thejvm.optionsfile must be updated.Swarm 14.0 does not support versions later than 7.5.2, so do not upgrade elasticsearch to 7.16.1. If you accidentally upgrade elasticsearch to a release after 7.5.2 it cannot be downgraded, you will need to create a new elasticsearch cluster and wait for a new Swarm Search Feed to populate it. Support for later elasticsearch versions is coming in 2022.
If you originally used our
configure_elasticsearch_with_swarm_search.pyscript to configure your elasticsearch 7.5.2 cluster you can use it to automatically make the jvm.options change and restart the service. Just upgrade to caringo-elasticsearch-search-7.0.3-1.noarch.rpm (released 2021-12-16) on each elasticsearch node and runconfigure_elasticsearch_with_swarm_search.py --upgrade. It will refresh your config files including jvm.options file, reinstall 7.5.2, and restart the service.
...