The right value of vm.max_map_count for elasticsearch

I found my cluster health is red,

and the es receive log events less and less

The phenomenon as follow:

So I checked the log of elasticsearch.

(more details:https://github.com/crazw/biglog/blob/master/elasticseatch.log

)

information:
http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html]];
nested: IOException[Map failed:
MMapIndexInput(path="/home/elasticsearch/data/elasticsearch/nodes/0/indices/logstash-2014.10.01/3/index/_hi_es090_0.tim")
[this may be caused by lack of enough unfragmented virtual address space or too
restrictive virtual memory limits enforced by the operating system,
preventing us to map a chunk of 3054244 bytes. Please review 'ulimit -v',
'ulimit -m' (both should return 'unlimited'), and 'sysctl vm.max_map_count'.
More information:
http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html]];
]]

So what should I set the value of vm.max_map_count .

Does anybody have such experience and give me a suggestion?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e16a6c75-af19-4947-bb0d-884fae426bbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.