Navigating to the Decommission page

When you access the Decommission page in the Grid Manager, you can see at a glance which nodes can be decommissioned.

Before you begin


  1. Select Maintenance > Decommission.
    The Decommission page appears, listing all grid nodes in a table. From this page, you can:
    • Determine which grid nodes can be decommissioned currently.
    • See the health of all grid nodes (assuming there are no disconnected nodes)
    • Sort the list in ascending or descending order by Name, Site, Type, or Has ADC.
    • Enter search terms to quickly find a particular node or group of nodes.
    • Use the page controls to move forward and backward through the list.

    screenshot of Decommission page

  2. 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 grid 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 message Description Steps to resolve
    No, node type decommissioning is not supported.

    StorageGRID Webscale does not allow you to decommission the primary Admin Node or an Archive Node.

    No, at least one grid node is disconnected.

    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 questionmark icon (gray): Administratively Down
    • blue question mark icon (blue): Unknown
    Go to step 3.
    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 "Understanding the ADC quorum" and Expanding a StorageGRID Webscale grid.
    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 ILM section of Administering StorageGRID Webscale.
    • Perform an expansion. Add new Storage Nodes so that the current Erasure Coding profile can continue to be used. See "Understanding the ADC quorum" and Expanding a StorageGRID Webscale grid.
  3. If decommissioning is possible for the node, determine which procedure you need to perform:
    If your grid includes... Go to...
    Any disconnected grid nodes Decommissioning disconnected grid nodes
    Only connected grid nodes Decommissioning connected grid nodes