Reviewing the considerations for decommissioning

You must understand the implications of removing grid nodes before you start this procedure. Removing a grid node impacts data security, the ILM policy, other maintenance procedures, and system operations.

Impact of decommissioning on data security

When you remove a Storage Node, data on the node is migrated to other grid nodes; however, this data is not completely removed from the decommissioned grid node. To permanently and securely remove data, you must wipe the decommissioned grid node’s drives after the decommission procedure is complete.

Impact of decommissioning on the ILM policy

As required, you can safely change the ILM policy while decommissioning API Gateway Nodes and Admin Nodes. However, you should not make any changes to the ILM policy while a Storage Node is being decommissioned.

Impact of decommissioning on other maintenance procedures

The decommission procedure requires exclusive access to some system resources, so you must confirm that no other maintenance procedures are running. Decommission procedures that involve Storage Nodes can be paused during certain stages to allow other maintenance procedures to run if needed, and resumed once they are complete.

Impact of decommissioning on system operations

When you remove a Storage Node, large volumes of object data must be transferred over the network. Although these transfers should not affect normal system operations, they can have an impact on the total amount of network bandwidth consumed by the StorageGRID Webscale system.

Tasks associated with Storage Node decommissioning are given a lower priority than tasks associated with normal system operations. Therefore, decommissioning does not interfere with normal StorageGRID Webscale system operations, and does not need to be scheduled for a period of system inactivity. Because decommissioning is performed in the background, it is difficult to estimate how long the process will take to complete. In general, decommissioning finishes more quickly when the system is quiet, or if only one Storage Node is being removed at a time.

Upon the successful decommissioning of a node, its services will be disabled and the node will be automatically shut down.