Boot Strap check failed

Hi
When i upgrade to elastic search 5.0.2 below error message received and its elastic search instance is getting closed.
[2016-11-30T00:47:09,525][INFO ][o.e.t.TransportService ] [m7H0n9h] publish_address {10.50.0.165:9300}, bound_addresses {[::]:9300}
[2016-11-30T00:47:09,531][INFO ][o.e.b.BootstrapCheck ] [m7H0n9h] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
ERROR: bootstrap checks failed
initial heap size [2147483648] not equal to maximum heap size [4294967296]; this can cause resize pauses and prevents mlockall from locking the entire heap
max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
memory locking requested for elasticsearch process but memory is not locked
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2016-11-30T00:47:09,538][INFO ][o.e.n.Node ] [m7H0n9h] stopping ...
[2016-11-30T00:47:09,640][INFO ][o.e.n.Node ] [m7H0n9h] stopped
[2016-11-30T00:47:09,640][INFO ][o.e.n.Node ] [m7H0n9h] closing ...
[2016-11-30T00:47:09,658][INFO ][o.e.n.Node ] [m7H0n9h] closed

I think the messages state pretty clearly what you need to do. What, in particular, do you want to see clarified?

Thanks for responding.
I like to know how to fix this issue.

I didnt face this issue previous version. I am little confused where to fix the issue. currently my Elasticsearch instance is AWS.

Read this: https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.