Handle rollback of node primary migration #42
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If the Patroni database fails to move, the node should back out of attempting to become primary. As-is, it simply forces forward but the domain aggregator fails to start. This might be a very difficult issue to solve, so still up in the air.
Leaning towards this being a non-issue, or maybe the case of locking the state transition to prevent another switch of the primary while one is still occurring. Going to try implementing the latter just to see how it goes.
This has been implemented in a safe way to handle the various failure modes.
/primary_node
key when performing abecome_primary()
action. Combined with the above, this will lock up the node if Patroni is in a bad state, which is somewhat less ideal but is a situation that requires administrator intervention.closed