ES freezes the server at startup

Elastic Stack Elasticsearch
10

Sigar can provide you this value in Java space with a call to
sigar.getMem().getTotal().

Thanks

On Dec 28, 11:15 am, Shay Banon shay.ba...@elasticsearch.com wrote:

The problem with having this setting set to true is the fact that people
have reported that it got to a stage where the OS crashed completely. Not
sure why it happened, but ES should not cause that with an out of the box
setting. Checking if there is enough memory is a good start, there is no API
for that in Java, but can try and use native code, I can play around with it
and see how it goes.

On Tue, Dec 28, 2010 at 7:14 PM, Paul ppea...@gmail.com wrote:

My two cents... This feature makes ES performance very reliable and
fixed some performance spikes that we encountered. I think it should
be defaulted to on.

It seems to me that the setting only causes problems when misused.
Along these same lines, what happens without this setting and someone
tries to allocate more mem than their system has and their JVM heap
reaches that point? I'd assume massive swapping leading to performance
degradation, which would only happen after hours or days of up time.
This seems like a ticking time bomb that would be much worse than fail
to start up.

Best case would be to check system memory before the mlockall call and
then gracefully exit with a descriptive error that you don't have
enough mem on your system.

Btw, this should probably be listed as a breaking change in the 0.14
release notes.

Thanks,
Paul

On Dec 27, 4:30 pm, Godefroy compreig...@gmail.com wrote:

Yes I think that I've not enough memory.
But ES should check if there is enough memory before themlockall,
nope ?

On 19 déc, 12:49, Clinton Gormley clin...@iannounce.co.uk wrote:

Why do ES crashes when bootstrap.mlockallis set to true ? It seems to
be dangerous... (It costs me 1 server, and I've lost lot of data)

What are your min and max memory settings, and how much memory do you
have available on the crashing server?

Could it be that you're trying to assign more memory than you have,
which causes all of your other processes to swap out?

clint