Hi Alex, thank you. I've run the command and also it shows that mlockall is set to true !
On Tuesday, February 11, 2014 2:33:49 PM UTC+1, Alexander Reelsen wrote: > > Hey, > > with recent elasticsearch versions (including newer 0.90), you can see if > bootstrap.mlockall setting is really applied in the nodes info. So make > sure setting it, was really successful. > > curl -XGET 'http://localhost:9200/_nodes' and search for mlockall, which > must be set to true. > > > --Alex > > > On Tue, Feb 11, 2014 at 10:08 AM, Vahid <[email protected] > <javascript:>>wrote: > >> Thank you Tony and Mark, >> >> atm I have no more information about the virtualization because it's our >> customer systems, maybe later I can provide more information regarding >> that. >> Other processes are our java applications which use ES to index and >> search data. >> >> From htop/top I can see that almost all the swap memory is used, and by >> running a bash script I can see how much swap space is used by which >> process and mosthly is used by ES. >> >> >> On Monday, February 10, 2014 10:44:00 PM UTC+1, Mark Walkom wrote: >> >>> How are you seeing this, ie what monitoring are you using? >>> Also, what is the "~3 gb other processes" exactly for? >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: [email protected] >>> web: www.campaignmonitor.com >>> >>> >>> On 11 February 2014 04:16, Vahid <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> ES is running on a ubuntu 64bit in VM environment with the following >>>> memory configuration: >>>> >>>> 12 gb total memory >>>> 5 gb elasticsearch >>>> ~3 gb other processes >>>> and 4 gb left for OS. >>>> >>>> ES cluster configured with 3 nodes. >>>> In the elasticsearch.yml bootstrap.mlockall set to true. On one of the >>>> nodes I can see that ES is using about 1gb of swap space. >>>> Also no warn log printed on the ES log file and only one node has this >>>> problem. >>>> >>>> Is there any settings missed there? >>>> >>>> Many thanks, >>>> >>>> Vahid >>>> >>>> -- >>>> 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/e9953624-3f35-4b86-a779-ac58dd0e30ba% >>>> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/791e40ad-c688-4de4-af78-c1f68c0d9569%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/b284a9c3-bf09-42e3-8393-8683e9d1425e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
