Hi Yogesh. I am not 100% sure of this, so if someone else posts a reply that differs from mine you should probably go with theirs, but I think this is correct behavior.
Unless there is another process demanding memory from the OS, there is no harm whatsoever in having the JVM consume all available RAM. It allows Elasticsearch to put more things in memory, serve more cache hits, etc. You definitely do not want the JVM to constantly run garbage collection so that it can return memory to the OS that it's just going to want to request again as soon as the system gets busy. You should make sure you are following recommended memory practices in http://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html. Hope that helps (and is accurate)! -joel On Sunday, March 22, 2015 at 3:30:57 AM UTC-4, Yogesh wrote: > > Hi, > > I have set up elasticsearch on one node and am using the Twitter river to > index tweets. It has been going fine with almost 50M tweets indexed so far > in 13 days. > When I started indexing, the JVM usage (observed via Marvel) hovered > between 10-20%, then started remaining around 30-40% but for the past 3-4 > days it has continuously been above 90%, reaching 99% at times! > I restarted elasticsearch thinking it might get resolved but as soon as I > switched it back on, the JVM usage went back to 90%. > > Why is this happening and how can I remedy it? (The JVM memory is the > default 990.75MB) > > Thanks > Yogesh > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0dd31898-83f8-414a-a85c-a8d5f1a64d4b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
