search

geerlingguy / ansible-role-elasticsearch

Ansible Role - Elasticsearch
https://galaxy.ansible.com/geerlingguy/elasticsearch/
MIT License
185 stars 209 forks source link

Different heap size for jvm causes issue when starting the es service #62

Closed deepbluemussel closed 4 years ago

deepbluemussel commented 4 years ago

Hello,

I couldn't start elasticsearch because of the heap map size that was different in min and max default variables in file defaults/main.yml. I mention that I adapted the playbook a bit for my use but the main.

Currently elasticsearch_heap_size_min and elasticsearch_heap_size_max are not the same . But according to java configuration comment, it should be the same. I confirm that when I changed the value to match, i was able to start the service.

Below the comment that mention that point:

You should always set the min and max JVM heap size to the same value. For example, to set the heap to 4 GB, set: -Xms4g -Xmx4g

cyntheticfox commented 4 years ago

It may also be worth noting that the official elasticsearch ansible role likewise implements an equivalency between the minimum and maximum allocation.

See https://github.com/elastic/ansible-elasticsearch/blob/master/templates/jvm.options.j2

stale[bot] commented 4 years ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

stale[bot] commented 4 years ago

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.