NotMasterException with duplicate node ids and minimum_master_nodes not met #32904
Description
Elasticsearch version 6.3.1
When an instances with copied data directories cluster with each other, we should see IllegalArgumentException .. found existing node .. with the same id but is a different node instance
However when minimum_master_nodes is not met, we see this instead:
NotMasterException .. not master for join request
Steps to reproduce:
- start ES from tar.gz, then stop ES
- cp -rp $ES_HOME $ES_HOME2
- set minimum_master_nodes: 2 in each config
- start ES on both nodes
[2018-08-16T07:29:43,468][INFO ][o.e.d.z.ZenDiscovery ] [gETA6zC] failed to send join request to master [{gETA6zC}{gETA6zC4T1ipiuSfOrpN_w}{vYiBS2AVQhSK0VITLJJ5tQ}{127.0.0.1}{127.0.0.1:9301}{ml.machine_memory=17179869184, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}], reason [RemoteTransportException[[gETA6zC][127.0.0.1:9301][internal:discovery/zen/join]]; nested: NotMasterException[Node [{gETA6zC}{gETA6zC4T1ipiuSfOrpN_w}{vYiBS2AVQhSK0VITLJJ5tQ}{127.0.0.1}{127.0.0.1:9301}{ml.machine_memory=17179869184, xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true}] not master for join request]; ], tried [3] times
- Remove
minimum_master_nodessetting, then the more accurate error appears:
[2018-08-16T07:27:47,066][INFO ][o.e.d.z.ZenDiscovery ] [gETA6zC] failed to send join request to master [{gETA6zC}{gETA6zC4T1ipiuSfOrpN_w}{iCnfSG48RTeWox4XqIN2cw}{127.0.0.1}{127.0.0.1:9300}{ml.machine_memory=17179869184, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}], reason [RemoteTransportException[[gETA6zC][127.0.0.1:9300][internal:discovery/zen/join]]; nested: IllegalArgumentException[can't add node {gETA6zC}{gETA6zC4T1ipiuSfOrpN_w}{mtW3yNGyQCq5znP5b-ZOZA}{127.0.0.1}{127.0.0.1:9301}{ml.machine_memory=17179869184, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}, found existing node {gETA6zC}{gETA6zC4T1ipiuSfOrpN_w}{iCnfSG48RTeWox4XqIN2cw}{127.0.0.1}{127.0.0.1:9300}{ml.machine_memory=17179869184, xpack.installed=true, ml.max_open_jobs=20, ml.enabled=true} with the same id but is a different node instance]; ]