Are you saying JVM is using 99% of the system memory or 99% of the heap? If it's 99% of the available heap that's bad and you will have cluster instability. I suggest increasing your JVM heap size if you can, I can't find it right now but I remember a blog post that used twitter as a benchmark and they also could get to ~50M documents with the default 1G heap.
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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0f990291-fa20-4bba-881f-3f378985c8c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
