This chapter describes the LEFTCLUSTER state and how to clear the state.
Occasionally, while CF is running, you may encounter the LEFTCLUSTER state, as shown by running the cftool -n command. A message will be printed to the console of the remaining nodes in the cluster. This can occur under the following circumstances:
Broken interconnects - All cluster interconnects going to another node (or nodes) in the cluster are broken.
Panicked nodes - A node panics.
Reboot - Shutting down a node with the reboot command.
Note
Nodes running CF should normally be shut down with the shutdown command or with the init command. If the reboot -f commandis executed, the node will be in the LEFTCLUSTER state.
The shutdown command or the init command will run the CF's Stop script that will allow CF to be cleanly shut down on that node. However, if you run the reboot -f, halt -f, or poweroff -f command, the CF's Stop script is not run, and the node will go down while CF is running. This will cause the node to be declared to be in the LEFTCLUSTER state by the other nodes.
If the Shutdown Facility (SF) is fully configured and running on all cluster nodes, it will try to resolve the LEFTCLUSTER state automatically. If SF is not configured and running, or the SF fails to clear the state, the state has to be cleared manually. This section explains the LEFTCLUSTER state and how to clear this state manually.
