Hello, Strange problem here (i think :slight_smile: ) I start elasticsearch on my laptop with docker-compose up -d es01, let the container start completly. Stop the containers with docker-compose stop. Then i do docker-compose up -d es01 again and elasticsearch gives me master not discovered or el…

Thanks, that's also useful. es02 says this about its network configuration: publish_address {172.19.0.2:9300}, bound_addresses {0.0.0.0:9300} However es01 says this: 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] It looks like es01 …

Master not discovered or elected yet, after docker compose stop and start

Elastic Stack Elasticsearch

system (system) Closed May 18, 2019, 5:48am 12

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

Topic		Replies	Views
Master not discovered or elected yet, an election requires 2 nodes with ids Elasticsearch	9	6721	February 24, 2021
Master not discovered or elected yet in docker envirement Elasticsearch docker	3	863	September 20, 2019
Master not discovered or elected yet, an election requires 2 nodes with ids Elasticsearch elastic-stack-security , docker	2	694	May 26, 2021
Master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes elasticsearch Elasticsearch docker	3	1657	February 14, 2020
Docker elasticsearch can't find master Elasticsearch	8	2049	December 19, 2019

Master not discovered or elected yet, after docker compose stop and start

Related topics