This is what it does - http://linux.die.net/man/2/mlockall Basically it prevents the memory being moved to swap.
Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [email protected] web: www.campaignmonitor.com On 30 January 2014 00:01, briche arnaud <[email protected]> wrote: > Hi, > > Following the advice on different blog post on production setup for > Elasticsearch, I'm using -Xms256m -Xmx256 and set bootstrap.mlockall to > True. > My guess was that the after restart, my Elasticsearch process would use > about 256m of ram, and that it's memory usage would remain quasi-constant > during it's lifetime. > But after the restart, my Elasticsearch process in using about 556m of ram. > > So, can someone please explain me the behaviour of mlockall ? > > THx in advance. > > -- > 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/1c761cf3-98d6-4010-bd46-50849c48b760%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/CAEM624Z31jzjtLaZVQ_GwSqf-x6ivDEH-2ObC_zPMwrzgd7ckA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
