No, node type decommissioning is not supported. |
StorageGRID Webscale does not allow you to decommission the primary Admin Node or an Archive Node.
|
None. |
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): Administratively Down
(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.
|