Hi all,


I have a question about the membership change implemented by Ratis.


Ratis implements the joint consensus (the complex one, according to the 
add/remove one server each time), and use LeaderStateImpl#stagingState to 
maintain the catch up progess of the new added raft node, thus won't append the 
OldNewConf into raft log until the new added peer catch up.


I consider there should be no un-available time during the membership change 
theoriocitally, even trying to change a single node cluster to a two node 
cluster, is that right ?


Thanks!
BR Glen

Reply via email to