Note: Do not use this procedure if you need to restart the entire cluster. Instead, see instructions for restarting the entire cluster in AWS, Azure, or GCP.
To reboot one node in a running cluster
-
Make sure there are no other nodes that are in an offline or re-syncing state. All disk groups must have zero offline disks and Resync = No.
# flashgrid-cluster - If the node is a database node, stop all local database instances running on the node.
-
Reboot the node using flashgrid-node command. It will gracefully put the corresponding failure group offline.
# flashgrid-node reboot -
Wait until the node boots up, all disks are back online, and resyncing operations are complete on all disk groups. All disk groups must have zero offline disks and Resync = No before it is safe to update another node.
# flashgrid-cluster - If the node is a database node start all previously stopped (Step 2) local instances.