Node Failure and Volume Protection State

If a node fails, volumes that have data stored on that node can be affected. For a volume with a replication factor of 3, a single node failure can cause the volume protection state to become Degraded. If another node fails, the volume’s state may become ReadOnly.

Although it is not recommended in Azure, if you created RF2 volumes and one node fails, they will become ReadOnly with a single node failure, and RF1 volumes will become Inaccessible if the node that the data is on fails.

In case all nodes that hold a volume’s replica fail, the volume becomes Inaccessible.

You can view the volume’s protection state by issuing the lbcli List Volumes command.

Sample Command

Bash
Copy

Sample Output

Bash
Copy

As you can see in the output, vol2 and vol3 are not in a FullyProtected volume protection state.

Now, you can use the lbcli list nodes command to identify which node has failed (the Cluster Admin command). In this command’s output you will see one of the following node states:

Node StateDescription
ActivatingNode is being activated and is currently unable to serve IOs. This state can occur after a node is reconnected to the network, coming up from reboot, or recovering from any other failure state. After the activation is complete, the node’s state transitions to Active.
ActiveNode is active and can serve IOs.
DeactivatingNode failure is detected and the Lightbits cluster software is changing the roles of other nodes in the cluster to keep data accessible.

Sample Command

Bash
Copy

Sample Output

Bash
Copy
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
Connecting Application Servers to Lightbits

© 2025 Lightbits Labs™

On This Page
Node Failure and Volume Protection State