Hi,
We are facing some issues while upgrading ES from 5.5.2 -> 7.8.1.
We have two nodes deployment setup. ES is installed in both nodes and both are master eligible.
In earlier version we used to have two master nodes. When one node goes down,
and the other node chosen to be a master automatically.
But in 7.8.1, this is not happening automatically, getting below issue in the ES.logs.
Issue:
[node-2] master not discovered or elected yet, an election requires a node with id
[GErKuIS3Q2i2qHWriSHphA], have discovered [{node-2}{GdjI2u5fRuawVOh-FiHT7g}
{LBnzTA94RZ6SDrYPKiM9bQ}{node-2.xxx.xxxx}{Ip_node_2:9300}{dimr}] which is not a quorum;
discovery will continue using [Ip_node_1:9300] from hosts providers and [{node-2}
{GdjI2u5fRuawVOh-FiHT7g}{LBnzTA94RZ6SDrYPKiM9bQ}{node-2.xxx.xxxx}{Ip_node_2:9300}
{dimr}] from last-known cluster state; node term 9, last-accepted version 193 in term 9
ID of node 1 = GErKuIS3Q2i2qHWriSHphA
ID of node 2 = GdjI2u5fRuawVOh-FiHT7g
below is the es.yml file config:
discovery.seed_hosts: ["node-1","node-2"]
cluster.initial_master_nodes: ["node-1","node-2"]
We are able form a cluster with these two nodes defined here and could see the data is replicated between these nodes.
We have not set "node.master" explicitly. as by default this is true.
would like to get some ideas on this issue. What changes do i need, to address this issue ?
Also we saw some voting exclusion API to exclude a node from voting process.
POST "/_cluster/voting_config_exclusions?node_names=node-1"
To configure this property, both nodes should be up and available.
In sceanrio like unexpected crash, hardware failure the node-1 will not be available
(which is chosen as master as per the initial election process).
Once, a master node is down is there a way to configure these properties ?
how to choose the other master eligible node as master automatically
(if the master chosen node is not available)? is there any configuration available in ES?