Note Check the solidDB Release Notes for any limitations that are associated with using a grid in the current release.
If a node in a solidDB grid stops responding to heartbeat messages, the following steps are performed.
1 The grid leader changes the membership state of the unresponsive node to MEMBER_DISCONNECTING.
2 The grid leader prepares the transaction, writes changes to the transaction log, and waits for acknowledgments that the transaction is prepared on other nodes.
3 All nodes prepare the transaction, write changes to the transaction log and send acknowledgment to the grid leader when the steps are complete.
4 When a majority of grid nodes have prepared the transaction, the grid leader commits the transaction, and writes the commit to the transaction log.
5 All grid nodes commit the transaction and the state of the unresponsive grid node becomes MEMBER_FAILED.
Note If the transaction execution fails, the transaction is rolled back and the membership state of the node reverts to MEMBER_ONLINE. After a while, if the node is still unresponsive, the grid leader restarts the attempt to set the node state to MEMBER_FAILED.
After the node status is set to MEMBER_FAILED, the Grid Availability Manager (GAM) balances the workload of the grid, see Node is removed or fails.
If the node starts responding again, the GAM automatically executes the ALTER GRID .. SET NODE .. ONLINE statement and the node is reconnected to the grid, see Processes involved in reconnecting a node.