Replies: 1 comment 4 replies
-
Hey @aley1 , it's correct, you can't change the node back to standby state, at least manually. In some circumstances, this can be done by framework automatically. This state is an extension to original Raft that serves to some special purposes:
Turning regular node to standby node may be dangerous for clients, especially, if you trying to convert leader to standby. Client might add uncommitted log entry without a chance to wait for a commit, and loose its write. In this case, uncommitted log entry will be eventually dropped from local WAL by a new elected leader. Client have to repeat its write request. Thus, converting to standby node can be done safely for followers only. Even in that case, during the conversion the node should not be able to transit from follower state to candidate state. Otherwise, the exception should be thrown. However, this is doable. According to that restrictions, is it still reasonable to add appropriate public method for you? If possible, could you please describe your use case and how the feature can be helpful? |
Beta Was this translation helpful? Give feedback.
-
Hi Sakno,
From the documentation and code, I can see that we can start a node as Standby node and later promote it to a Node that can be elected as an Leader. However it looks like it's not possible to change Node back to a Standby node later when the cluster is formed and running.
Do you plan to introduce this functionality?
It is actually important to the project I am working on.
Beta Was this translation helpful? Give feedback.
All reactions