I'm working on setting up a new cluster (new hardware), and I'm seeing unexpected heap behavior while doing some load testing. Elasticsearch 5.2.2, OpenJDK 8, SL7 (i.e. RHEL7). All nodes are configured with 16gb heap, verified in the logs and API, yet GC appears to be running around 1.5gb. This is under constant indexing, a mix of log-like and document-like (updating) behavior. One node stands out, but I don't see anything else unusual about it (it's not the master, and all nodes are configured identically with puppet). Any suggestions?
Right, hence my confusion. API clearly shows 16gb though [1]. The nodes were installed and configured with the elastic/elasticseach puppet forge module, and are run under systemd. Now that I've loaded more data the heap usage has gone up on the busier nodes [2], so maybe it was just a matter of getting more activity. This is a much larger cluster than we were using before.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.