You can decommission and permanently remove one or more Storage Nodes, Gateway Nodes, or non-primary Admin Nodes from the StorageGRID system.
About this task
You cannot decommission a grid node if doing so will leave the StorageGRID in an invalid state. The following rules are enforced:
- You cannot decommission the primary Admin Node.
- You cannot decommission Archive Nodes.
- You cannot decommission a Storage Node if its removal would affect the ADC quorum.
- You cannot decommission a Storage Node if it is required for the active ILM policy.
- You cannot decommission a connected grid node if your grid includes any disconnected grid nodes (nodes whose health is Unknown or Administratively Down). If your grid includes any disconnected nodes, you must bring them back online, recover them, or decommission them while they are disconnected.
- You cannot decommission a node that is part of an HA group. You must first remove the node from the HA group.
Note: When you decommission a Storage Node, the following alarms might be raised:
- VSTU (Object Verification Status). This notice-level alarm indicates that the Storage Node is going into maintenance mode during the decommission process.
- CASA (Data Store Status). This major-level alarm indicates that the Cassandra database is going down because services have stopped.