{"type": "server", "timestamp": "2019-11-04T12:12:27,916Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "elastic", "node.name": "elastic-es-default-0", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{elastic-es-default-0}{R6HYNNymSF-jhqz5y3EJuQ}{kWMPQe05TUmH9jii7PVzcA}{10.32.0.32}{10.32.0.32:9300}{dilm}{ml.machine_memory=4294967296, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305] from hosts providers and [{elastic-es-default-0}{R6HYNNymSF-jhqz5y3EJuQ}{kWMPQe05TUmH9jii7PVzcA}{10.32.0.32}{10.32.0.32:9300}{dilm}{ml.machine_memory=4294967296, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" }
{"type": "server", "timestamp": "2019-11-04T12:12:28,008Z", "level": "WARN", "component": "r.suppressed", "cluster.name": "elastic", "node.name": "elastic-es-default-0", "message": "path: /_bulk, params: {}",
"stacktrace": ["org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized, SERVICE_UNAVAILABLE/2/no master];",
Hey @sathia.thayathil,
Apologies for late reply. What was the operator version you've used? There was a bug with the same symptoms (https://github.com/elastic/cloud-on-k8s/pull/1977) and it was fixed in beta1. If you are running beta already, it would be helpful if can you provide more details about your setup - elasticsearch resource specification, operator logs and more logs from elasticsearch. Also, is this happening every time?
Thanks,
David