Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse

SNMP Commands

Storage cluster nodes are controlled through the SNMP action commands. The following OIDs allow disabling nodes and volumes with nodes from a storage cluster:

...

To gracefully shut down a Swarm node, the string shutdown is written to the castorShutdownAction OID. Writing the string reboot to this OID causes a Swarm node to reboot.

...

The Retire action is used to permanently remove a node or a volume within a node from the cluster. This action is intended for retiring legacy hardware or preemptively pushing content away from a volume with a history of I/O errors. Retired volumes and nodes are visible in the Swarm Admin Console until the cluster is rebooted.

Seehttps://perifery.atlassian.net/wiki/spaces/public/pages/2443811993/Retiring+Hardware#Retire-Rate and https://perifery.atlassian.net/wiki/spaces/public/pages/2443811993/Retiring+Hardware#Retiring-Volumes.

Note

The Retire action may take an extended amount of time to complete and requires at least three health processor cycles.

...

Each volume is given a unique name within the node – the device string from the vols line in the configuration file. To retire a volume, the name is written as a string to the castorRetireAction OID. The volume retirement process is initiated immediately upon receipt and the action cannot be aborted after it starts.

...

To retire a node and all volumes, the all string is written to the castorRetireAction OID. The node retirement process is initiated immediately upon receipt and the action cannot be aborted after it starts.

Note

Warning

Verify the cluster has enough free space and nodes to store the objects from the retiring volume. For subclusters, this applies to the subcluster where the retiring volume resides. The retiring node cannot complete the retirement process until adding additional nodes if the number of nodes in the cluster or subcluster do not have enough space to store at least two replicas of all objects.

The Retire action does not require the configured default replicas (policy.replicas default) are maintained to complete retirement. Messages are logged indicating sufficient replicas cannot be created if there are not enough nodes to maintain the minimum number of replicas.

...