{"id":14913,"date":"2020-02-05T08:08:29","date_gmt":"2020-02-05T08:08:29","guid":{"rendered":"https:\/\/dbtut.com\/?p=14913"},"modified":"2021-02-06T09:23:56","modified_gmt":"2021-02-06T09:23:56","slug":"how-to-configure-elasticsearch-heap-size-to-change-max-memory-size","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2020\/02\/05\/how-to-configure-elasticsearch-heap-size-to-change-max-memory-size\/","title":{"rendered":"How To Configure Elasticsearch Heap Size to Change Max Memory Size"},"content":{"rendered":"

This article contains information about what is elasticsearch heap size, garbage collector and elasticsearch heap size recommended.<\/p>\n

What is Elasticsearch Heap Size?<\/h2>\n

It is a very important setting for ElasticSearch. In order for this setting to be set correctly, the system must be well monitored. In short, we determine the amount of memory that Elasticsearch will allocate at the beginning and maximum memory usage, with this config.<\/p>\n

Before configuring Heap Size, I will talk about the heap memory concept to monitor heap size correctly. Java applications use the “stack” and “heap” methods to save data to memory.<\/p>\n

In Stack type, the operating system manages whether the data will be stored or deleted in memory.<\/p>\n

In Heap type, the application manages memory usage and cleaning. In Java, objects are stored in the heap memory and thanks to the structures called Garbage Collector, heap memory management is provided.<\/p>\n

What is Garbage Collector?<\/h3>\n

In Java, memory management is done in the background with JVM and the Garbage Collector included in it. Garbage Collector simplifies application development and shortens coding time with automatic memory management. Again, Garbage Collector is able to deal with the problem of leaking memory areas caused by coding errors.<\/p>\n

Garbage Collection is an automated memory management mechanism. it looks at Heap memory, detects used objects and deletes non-referenced ones. The space occupied by unused \/ non-referenced objects is cleared from memory and this increases available free memory. The mechanism that performs this process is called Garbage Collector.<\/p>\n

Excessive heap size can be used for caching, but excessive heap size can cause pauses on the garbage collector. Return to end-user can be very long when GC stops.<\/p>\n

When the long pause is experienced, access does not occur in distributed systems such as Elasticsearch, as the node may be isolated from the cluster. There is no reading or writing operation on this node. If the node is a Master node, a new Master node can be selected. If the node is data node, it may cause the shards to be placed in other data nodes. In this case, it increases the network traffic, the input-output operations on the disk and the load of the cluster.<\/p>\n

Briefly<\/strong>, if heap size is set to be less than you need, other problems may be encountered besides memory errors.<\/p>\n

Elasticsearch Heap Size Recommended<\/h3>\n