If there are any config for garbage collection in Elastic search

(Dinesh) #1

Please suggest if there are any config for garbage collection.

Dinesh D

(Mark Walkom) #2

Elasticsearch does its own GC.

(Dinesh) #3

So we cant ableconfigure it right ?

Dinesh D

(Mark Walkom) #4

Why do you want to do that?

(Dinesh) #5

My JVM memory goes almost 75%

(Mark Walkom) #6

Then altering the GC settings for Elasticsearch will not solve anything, you just delay the problem and make it worse when it happens.

Is the GC causing big problems?

(Christian Dahlqvist) #7

Heap usage usually gets to 75% before GC is triggered. As long as it goes down after this it is generally a nice and healthy pattern. If you are constantly at or around 75% heap usage you may need to increase your heap size by scaling up or out.

(Dinesh) #8

Thanks, I will increase the xmx and xms to 4 GB

(Admin_Hack) #9

If you simply want to decrease the amount of memory that Elasticsearch is
using, you need to change your heap size (via the HEAP_SIZE environment
variable). That controls the total memory allocated to Elasticsearch.

Echoing what Binh said...try not to change the field-data settings unless
you know what you are doing. You should not enable soft references for
field-data, this is a very bad option. It causes excessive GC thrashing
and is not needed (especially now that 1.0 has circuit breaker logic built
in). Similarly, the time expiration on field-data is typically a poor
option, since it unnecessarily thrashes the GC too.
You can also increase the swap storage space or install add swap memory. :slight_smile:

(system) #10

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.