Cluster Changes to speed up master detection

Hello, I have a 4 node cluster on elasticsearch. I am using 7.6.0

Every time I made a change to docker compose and need to rebuild it node, it keeps losing track of where is the master. It takes a few hours for it to go back to green.

Everything is manually hard coded. including IPs and certificates.

is there a setting I need to tweak to allow for quick changes in cluster?

Below is be docker compose section. It pretty much follows the directive of whats on the support docs of how to build it.


  - node.name=es02
  - node.ingest=true
  - cluster.name=cluster01
  - discovery.seed_hosts=es01,es03,es04
  - cluster.initial_master_nodes=es01,es02,es03,es04
  - ELASTIC_USERNAME=$ELASTIC_USERNAME
  - ELASTIC_PASSWORD=$ELASTIC_PASSWORD
  - bootstrap.memory_lock=true
  - xpack.license.self_generated.type=basic
  - xpack.security.enabled=true
  - xpack.security.http.ssl.enabled=true
  - xpack.security.http.ssl.key=$CERTS_DIR/es02/es02.key
  - xpack.security.http.ssl.certificate_authorities=$CERTS_DIR/ca/ca.crt
  - xpack.security.http.ssl.certificate=$CERTS_DIR/es02/es02.crt
  - xpack.security.transport.ssl.enabled=true
  - xpack.security.transport.ssl.verification_mode=certificate
  - xpack.security.transport.ssl.certificate_authorities=$CERTS_DIR/ca/ca.crt
  - xpack.security.transport.ssl.certificate=$CERTS_DIR/es02/es02.crt
  - xpack.security.transport.ssl.key=$CERTS_DIR/es02/es02.key
  - "ES_JAVA_OPTS=-Xms80g -Xmx80g"

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