Elasticsearch - Bootstrap checks failing

Question

I'm trying to use the Flink 5.x Elasticsearch sink connector to insert data to ES 5.2.1 instance hosted on a tiny VM.

As this is a tiny VM in development mode, I cant get it to start up to accept TransportClient remote client connections on 9300 without failing the bootstrap checks.

[2017-02-17T09:02:48,581][INFO ][o.e.n.Node               ] [Z_fiBnl] starting ...
[2017-02-17T09:02:48,866][INFO ][o.e.t.TransportService   ] [Z_fiBnl] publish_address {xxxxxx:9300}, bound_addresses {127.0.0.1:9300}
[2017-02-17T09:02:48,878][INFO ][o.e.b.BootstrapChecks    ] [Z_fiBnl] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks
ERROR: bootstrap checks failed
max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
max number of threads [1024] for user [xxx] is too low, increase to at least [2048]
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk

I've played around with the below settings but just cant get it to startup(http clients on 9200 work fine)

transport.publish_host: 0.0.0.0
transport.bind_host: 0.0.0.0
http.host: "xxx"
http.host: 169.117.72.167
network.host: 0.0.0.0
network.publish_host: 0.0.0.0

Note that ES is running on a tiny VM just for dev purposes and I don't have access to change for ex. the file descriptor limits on this box.

Answer 1

max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]

ulimit -n 65536 

or set nofile to 65536 in /etc/security/limits.conf

max number of threads [1024] for user [xxx] is too low, increase to at least [2048]

ulimit -u 2048

Or set the nproc value to 2048 or above in /etc/security/limits.conf before starting elasticsearch.

max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

set vm.max_map_count=262144 in /etc/sysctl.conf then do sysctl -p

If you want to run elasticsearch in development environment despite failing bootstrap checks:

Set the following in your elasticsearch.yml

transport.host: 127.0.0.1
http.host: 0.0.0.0

Please note you cant form a cluster in development mode. Dont use elasticsearch that is failing bootstrap checks in production!!

Answer 2

Try configuring your elasticsearch.yml file this way :

network.host: 0.0.0.0 http.port: 9200 transport.host: localhost transport.tcp.port: 9300