Closed MarcusCaepio closed 2 years ago
Hi @MarcusCaepio, Thanks for reporting this. Automatic heap sizing seem to be a new feature coming in 7.11 and this role hasn't been updated to handle it yet.
Meanwhile, a workaround would be to override the jvm.options
file without specifying -Xms
and -Xmx
using es_config_jvm
(see https://github.com/elastic/ansible-elasticsearch#how-to-override-configuration-files-provided-by-ansible-elasticsearch).
Related to #738
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
still valid
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity since being marked as stale.
Hi all, after installing a new cluster on 7.11 with this role, I mentioned that the Bundled JDK heap size is set to 2GB. According to the docs at https://www.elastic.co/guide/en/elasticsearch/reference/7.11/important-settings.html#heap-size-settings the heap size is set automatically, when the bundled JDK is used and we should let it like that. As I did not set es_heap_size in my Playbook, I thought, the automatic heap size would work. But in the jvm.conf the values
are given. Imho, this should not be there, when the bundled JDK is used an no es_heap_size value is given. OS: UIbuntu 20.04.2 LTS Role Version: 7.10.2
Thanks and cheers, Marcus