Kevin Gibson

Try increasing es-data nodes to at least 4 GB.

@mootezbessifi In my experience, I was giving java heap more RAM than container was able to provide, so while pod worked fine for a while, as time went on, Java...

@mootezbessifi That is essentially your call and depends what kind of data ES needs to handle. To resolve java heap out of memory errors, start by checking how much RAM...

I have same question, about whether or not swaps are disabled be default. Any idea how to verify that java heap limits are taking care of this?

Same issue on stateless configuration as well. Very curious - this was just working fine recently. What happened?

Pod log: -> Downloading mapper-murmur3 from elastic [=================================================] 100% -> Installed mapper-murmur3 [2018-10-10T19:04:23,328][INFO ][o.e.n.Node ] [es-master-stateless-68bc4b596-6h5j7] initializing ... [2018-10-10T19:04:24,207][INFO ][o.e.e.NodeEnvironment ] [es-master-stateless-68bc4b596-6h5j7] using [1] data paths, mounts [[/data (/dev/sda1)]], net...

https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html

The issue is not with my environment as I'm able to build cluster with different configs. Wondering if there is issue in new 6.3.0 image?

if running on k8s, how can run.sh be modified? Is quay.io/pires/elasticsearch:6.2.4 image still compatible?

Digging deeper into errors, I found my issue documented here https://github.com/pires/kubernetes-elasticsearch-cluster/issues/64 Adding `NETWORK_HOST` value `_eth0_` to es-master.yml resolved issue as nodes were not obtaining connectivity.