A big part of raft is running an odd number of servers But we are scaling nodes 1 at a time and there are a lot of times where we have only 2 nodes in the cluster
If the new node goes down and comes back up is it possible it can become the leader even though it has less transactions than the existing node? Since there are only 2 nodes - is there a guarentee that always the node that has the highest transaction id will be elected the leader? We are seeing 0. Exisiting 1 node cluster with node 1 as the leader 1. New node 2 gets added 2. Node 1 and 2 are healthy 3. Node 2 goes down 4. Node 1 is in candidate state 5. Node 2 comes back 6. Node 2 becomes leader Shouldn't node 1 be always the leader?
