solidDB Help : solidDB Grid : Grid nodes : Processes involved in adding and removing grid nodes : Processes involved in permanently removing a node
  
Processes involved in permanently removing a node
Note Check the solidDB Release Notes for any limitations that are associated with using a grid in the current release.
The statement ALTER GRID .. DROP NODE permanently removes a node from a solidDB grid as a synchronously replicated transaction that is started and coordinated by the grid leader, see Removing a node from a grid.
When the ALTER GRID .. DROP NODE statement is executed, the following steps are performed:
1 The grid leader stops replication with the grid node that is being dropped.
2 The grid leader changes the membership state of the node that is being dropped to MEMBER_BEING_DROPPED.
3 The grid leader prepares the transaction, writes changes to the transaction log, and waits for acknowledgments that the transaction is prepared on other nodes (including the node that is being dropped).
4 The node (that is being dropped) stops replication from the leader. All other followers stop replication from the grid node that is being dropped. All nodes prepare the transaction, write changes to the transaction log and send an acknowledgment to the grid leader when the steps are complete.
5 When a majority of grid nodes have prepared the transaction, the grid leader commits the transaction, and writes the commit to the transaction log.
6 All grid nodes commit the transaction and the new grid node state becomes NOT_MEMBER (a transitory state; the corresponding row is removed from the SYS_GRID_NODES table as part of the commit). The node that is being dropped stops the replication from other nodes as part of the commit.
7 When the transaction is complete, the information about the node is discarded and the state of the node can no longer be queried.
Note If the transaction execution fails, the transaction is rolled back and the membership state of the node reverts to MEMBER_ONLINE.
8 After commit, the dropped node takes the action specified in the ALTER GRID .. DROP NODE. statement (KEEP, RECYCLE, or SHUTDOWN).
After the node is removed, the Grid Availability Manager (GAM) balances the workload of the grid, see Node is removed or fails.
Go up to
Processes involved in adding and removing grid nodes