When you access the Decommission Nodes page in the Grid Manager, you can see at a glance which nodes can be decommissioned.
Before you begin
- You must be signed in to the Grid Manager using a supported browser.
- You must have the Maintenance or Root Access permission.
Procedure
-
Select Maintenance. Then, in the Maintenance Tasks section of the menu, select Decommission.
The Decommission page appears.
- Click the Decommission Nodes button.The Decommission Nodes page appears. From this page, you can:
- Determine which grid nodes can be decommissioned currently.
- See the health of all grid nodes
- Sort the list in ascending or descending order by Name, Site, Type, or Has ADC.
- Enter search terms to quickly find particular nodes.
- Use the page controls to move forward and backward through the list.
For example, this page shows all grid nodes in a single data center. The Decommission Possible column indicates that you can decommission the non-primary Admin Node, the Gateway Node, and two of the five Storage Nodes.
-
Review the Decommission Possible column for each node you want to decommission.
If a grid node can be decommissioned, this column includes a green check mark, and the left-most column includes a check box. If a node cannot be decommissioned, this column describes the issue. If there is more than one reason a node cannot be decommissioned, the most critical reason is shown.
Decommission Possible reason Description Steps to resolve No, node type decommissioning is not supported. You cannot decommission the primary Admin Node or an Archive Node.
None. No, at least one grid node is disconnected. Note: This message is shown for connected grid nodes only.You cannot decommission a connected grid node if any grid node is disconnected.
The Health column includes one of these icons for grid nodes that are disconnected:
(gray): Administratively Down
(blue): Unknown
Go to step 4. No, one or more required nodes is currently disconnected and must be recovered. Note: This message is shown for disconnected grid nodes only.You cannot decommission a disconnected grid node if one or more required nodes is also disconnected (for example, a Storage Node that is required for the ADC quorum).
- Review the Decommission Possible messages for all disconnected nodes.
- Determine which nodes cannot be decommissioned because they are required.
- If the Health of a required node is Administratively Down, bring the node back online.
- If the health of a required node is Unknown, perform a node recovery procedure to recover the required node.
No, member of HA group(s): x. Before you can decommission this node, you must remove it from all HA groups. You cannot decommission an Admin Node or a Gateway Node if a node interface belongs to a high availability (HA) group.
Edit the HA group to remove the node's interface or remove the entire HA group. See the instructions for administering StorageGRID. No, site x requires a minimum of n Storage Nodes with ADC services. Storage Nodes only. You cannot decommission a Storage Node if not enough nodes would remain at the site to support ADC quorum requirements.
Perform an expansion. Add a new Storage Node to the site, and specify that it should have an ADC service. See information about the ADC quorum. No, the ILM policy requires a minimum of n Storage Nodes for erasure coding. Storage Nodes only. If the active ILM policy uses rules that specify objects be erasure coded, you cannot decommission a Storage Node if not enough nodes would remain to support the erasure coding scheme selected in the Erasure Coded profile.
- Create a new active ILM policy. Only use rules that make replicated copies or select an Erasure Coding profile that uses a different erasure coding scheme. See the instructions for administering StorageGRID.
- Perform an expansion. Add new Storage Nodes so that the current Erasure Coding profile can continue to be used. See information about the ADC quorum and the instructions for expanding StorageGRID.