Hello, After step 4 above, Ignite will detect that original primary Node A is up, so all the updates happened while Node A was down will be applied to Node A so thay it is latest and it will marked as Primary again. Till the time this process is completed, Node B will still be considered as primary.
Regards, Gaurav On 14-Sep-2018 9:23 PM, "eugene miretsky" <[email protected]> wrote: > What is the process when a node goes down and then restarts? > > Say backups = 1. We have node A that is primary for some key, and node B > that is back up. > > Node A goes down and then restarts after 5 min. What are the steps? > 1) Node A is servicing all traffic for key X > 2) Node A goes down > 3) Node B starts serving all traffic for key X (I guess the clients detect > the failover and start calling node B ) > 4) Node A comes back up > 5) WAL replication is initiated > > What happens next? When does node A become the primary again? How are > in-flight updates happen? > >
