Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

Heapsize is set to 2GB when es_heap_size is not set #776

Closed
MarcusCaepio opened this issue Feb 17, 2021 · 6 comments
Closed

Heapsize is set to 2GB when es_heap_size is not set #776

MarcusCaepio opened this issue Feb 17, 2021 · 6 comments

Comments

@MarcusCaepio
Copy link

MarcusCaepio commented Feb 17, 2021

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

-Xms2g
-Xmx2g

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

@jmlrt jmlrt added the bug label Feb 24, 2021
@jmlrt
Copy link
Member

jmlrt commented Feb 24, 2021

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).

@jmlrt
Copy link
Member

jmlrt commented Feb 24, 2021

Related to #738

@botelastic
Copy link

botelastic bot commented May 25, 2021

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.

@jmlrt
Copy link
Member

jmlrt commented May 25, 2021

still valid

@botelastic botelastic bot removed the triage/stale label May 25, 2021
@botelastic
Copy link

botelastic bot commented Aug 23, 2021

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.

@botelastic
Copy link

botelastic bot commented Sep 22, 2021

This issue has been automatically closed because it has not had recent activity since being marked as stale.

@botelastic botelastic bot closed this as completed Sep 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants