Bootstrap checks keeps failing

Hi to all,
Im facing issues starting up my Elasticsearch cluster.
We have an active-stdby architecture that we manage on our own.
So, before im running the elasticsearch, im modifying (runtime) it's configuration on each node. one is set with master=True, and the other with master=False.
We have a constant ip to each container, and a constant ip to the active container.
the configuration for the master node is as seen below

bootstrap.memory_lock: true
cluster.initial_master_nodes: ["{EXT_HOSTNAME}"] dn-elasticsearch #discovery.seed_hosts: [] http.bind_host: http.port: {ELASTICSEARCH_PORT}
indices.memory.index_buffer_size: 512mb
indices.memory.min_index_buffer_size: 32mb
network.bind_host: true
node.ingest: true
node.master: true ${EXT_HOSTNAME} /techsupport
path.repo: /elasticsearch_backup
transport.port: 9300

the bootstrap check keeps failing no matter what im doing..

{"type": "server", "timestamp": "2020-02-26T12:11:15,066Z", "level": "INFO", "component": "o.e.d.DiscoveryModule", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "using discovery type [zen] and seed hosts providers [settings]" }
{"type": "server", "timestamp": "2020-02-26T12:11:15,924Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "initialized" }
{"type": "server", "timestamp": "2020-02-26T12:11:15,924Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "starting ..." }
{"type": "server", "timestamp": "2020-02-26T12:11:16,042Z", "level": "INFO", "component": "o.e.t.TransportService", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "publish_address {}, bound_addresses {}" }
{"type": "server", "timestamp": "2020-02-26T12:11:16,142Z", "level": "INFO", "component": "o.e.b.BootstrapChecks", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "bound or publishing to a non-loopback address, enforcing bootstrap checks" }
ERROR: [3] bootstrap checks failed
[1]: initial heap size [4294967296] not equal to maximum heap size [17179869184]; this can cause resize pauses and prevents mlockall from locking the entire heap
[2]: max file descriptors [64000] for elasticsearch process is too low, increase to at least [65535]
[3]: memory locking requested for elasticsearch process but memory is not locked
{"type": "server", "timestamp": "2020-02-26T12:11:16,151Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "stopping ..." }
{"type": "server", "timestamp": "2020-02-26T12:11:16,177Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "stopped" }
{"type": "server", "timestamp": "2020-02-26T12:11:16,177Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "closing ..." }
{"type": "server", "timestamp": "2020-02-26T12:11:16,187Z", "level": "INFO", "component": "o.e.n.Node", "": "dn-elasticsearch", "": "dn55-ncc0", "message": "closed" }

can someone please help me figure out what am I doing wrong?

best regards,

The problems you need to address are spelled out in detail in this log message:

damn, im stupid.
I was sure if failed due to my network configuration and those are just non-related errors.

thank you very much.

1 Like

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