Github user asdf2014 commented on the issue:
https://github.com/apache/zookeeper/pull/301
Hi @afine . Thanks for your comments. Your consider is entirely correct.
But I found the [PR#16937](https://github.com/elastic/elasticsearch/pull/16937)
from `elasticsearch`. And every node in our `elasticsearch` cluster always be
set as huge
[`ES_HEAP_SIZE`](https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html)
value. Then it just spend a few second when the `elasticsearch` instance start
up. However, the server node in `zookeeper` cluster usually we don't assign too
large memory. So, the `zookeeper` as daemon instance will get more benefit from
it. (PS, same tuning in
[Cassandra](https://tobert.github.io/tldr/cassandra-java-huge-pages.html),
[Jenkins](https://jenkins.io/blog/2016/11/21/gc-tuning/) etc.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
