Thanks Uwe. As I mentioned earlier, I did guess that VIRT doesn't indicate RAM consumption.
What I am concerned about is the 3rd row which shows memory and indicates that out of the total 50g, 43g is in use. Once this number crosses 45g, my other databases start behaving badly. Problem is, even after I kill all the processes, this doesn't go down. (Attaching snapshot of top after killing all processes). Right now what I do is reboot the system every three days which is the time it takes to gradually fill the memory with something (I have no clue what that is). Though I think the max file descriptors wouldn't be the culprit for this? I haven't changed that yet. On Mon, Mar 30, 2015 at 3:19 AM, Uwe Schindler <uwe.h.schind...@gmail.com> wrote: > You should read: > http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html > > Maybe this allows you to figure out what's going on! VIRT means nothing > about consumption, you should look at RES. > > Thanks, > Uwe > > > Am Sonntag, 29. März 2015 22:23:00 UTC+2 schrieb Yogesh: >> >> Hi, >> >> I have a single node ES setup (50GB memory, 500GB disk, 4 cores) and I >> run the Twitter river on it. I've set the ES_HEAP_SIZE to 5g. However, when >> I do "top", the ES process shows the VIRT memory to be around 34g. That >> would be I assume the max mapped memory. The %MEM though always hovers >> around 10% >> >> However, within a few days post-reboot, the memory used keeps going up. >> From 10g to almost 50g (as shown in the third line) because of which my >> other dbs start behaving badly. Below is the snapshot of "top". Despite the >> fact that VIRT and %MEM still hover around the same 34g and 10% >> respectively. >> >> Please help me understand where is my memory going over time! My one >> guess is that Lucene is eating it up. How do I remedy it? >> >> Thanks-in-advance! >> >> >> >> <https://lh3.googleusercontent.com/-zD9y4f2Eqqk/VRhdtX2XtTI/AAAAAAAAAN8/aq8-wxm2bBg/s1600/top.png> >> >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/kTDNDJwxOzA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/c6e834ab-77c4-4a99-9307-b6b3baf0d232%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/c6e834ab-77c4-4a99-9307-b6b3baf0d232%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CADM0w%3Di5%2B_Cd-swP3f58jm-cE%2B7ULsq6QwfafQjsmka47h3fkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
