Arctera

In an Azure environment, an InfoScale cluster node may panic if any of the node is rebooted using Azure portal [3930926]

In an Azure environment, an InfoScale cluster node may panic if any of the node is rebooted using Azure portal.

This issue occurs if you have enabled I/O fencing for the cluster.

When you reboot any cluster node using Azure portal, the time required for reboot is more than the time taken by the fencing module to detect a network partition and to perform the fencing operation. As a result, the node that is rebooted or any other node in the cluster may panic.

Workaround: Increase the LLT peerinact timeout value to 120 seconds (2 mins). The default LLT peerinact timeout value is 16 seconds.

Increasing the LLT peerinact timeout value delays the fencing race during which time the node reboot operation is complete.

To increase the LLT peerinact timeout, run the following command on any of cluster node that is active:

lltconfig -T peerinact:12000

In an Azure environment, an InfoScale cluster node may panic if any of the node is rebooted using Azure portal [3930926]

In this article