Determining the maintenance priority of storage nodes

Virtual Storage Platform One SDS Block System Administrator Guide

Version
1.15.x
Audience
anonymous
Part Number
MK-24VSP1SDS001-02

If more than one storage node in the following status exists in "the storage node group to be dealt with" determined before running the workflows in Action to be taken when "Alerting" is shown in the storage node health status, make sure to determine the order in which you troubleshoot the storage nodes:

Status:

  • TemporaryBlockage

  • MaintenanceBlockage

  • InstallationFailed

Note:

If you are unable to address the target storage node immediately, such as when part procurement takes a long time, target the storage node with the highest priority.

When there are three cluster master nodes in the storage cluster

Take action starting for the storage node with the highest priority (the smallest number in the "Priority" column) in the table below. If there are two or more storage nodes with the highest priority, troubleshoot any of the storage nodes.

Type of storage node

Precedence

Cluster master node

1

Cluster worker node

2

When there are five cluster master nodes in the storage cluster

Perform the following procedure to verify the precedence.

  1. Verify the number of cluster master nodes in the storage cluster that are in one of the following statuses: blocked, could not be blocked1, or could not be removed2.

  2. See the list of storage controllers, and then record the ID of the storage node (hereinafter referred to as "storage node with storage controller in the status of TwoNodesDown") that is "standbyStorageNodeId" or "secondaryStandbyStorageNodeId" of the storage controller whose status is "TwoNodesDown" .

  3. Check whether each target storage node in the status that troubleshoots the failure is a cluster master node or a cluster worker node.

  4. Based on the check results in step 1 through step 3, make sure to take actions on the failure in the order from the storage node with the highest priority (the smallest number in the Precedence column) by following the tables. The storage nodes with the same priority have the same precedence.

    • The number of cluster master nodes that are in any of the following statuses: blocked, could not be blocked1, or could not be removed2 is 1 or less.

      Type of storage node

      Precedence

      "Storage node with storage controller in the status of TwoNodesDown" and cluster master node

      1

      "Storage node with storage controller in the status of TwoNodesDown" and cluster worker node

      2

      Not "storage node with storage controller in the status of TwoNodesDown" but cluster master node

      3

      Not "storage node with storage controller in the status of TwoNodesDown" but cluster worker node

      4

    • The number of cluster master nodes that are in any of the following statuses: blocked, could not be blocked1, or could not be removed2 is 2.

      Type of storage node

      Precedence

      "Storage node with storage controller in the status of TwoNodesDown" and cluster master node

      1

      Not "storage node with storage controller in the status of TwoNodesDown" but cluster master node

      2

      "Storage node with storage controller in the status of TwoNodesDown" and cluster worker node

      3

      Not "storage node with storage controller in the status of TwoNodesDown" but cluster worker node

      4

      1. If the storage node is either blocked or could not be blocked, the status will be one of the following:

      "TemporaryBlockage","MaintenanceBlockage","PersistentBlockage",

      "InstallationFailed","TemporaryBlockageFailed","MaintenanceBlockageFailed",

      "RemovalFailedAndTemporaryBlockage","RemovalFailedAndMaintenanceBlockage",

      "RemovalFailedAndPersistentBlockage","RemovalFailedAndMultipleFailures"

      2. If the storage node could not be removed, the status contains the string "RemovalFailed".