There
is a problem with the local network on which the metadata servers communicate.
The problem may be:
- A network fault. A local network fault can occur if there is a bad Ethernet
adapter in an engine or the Ethernet cable is not connected between the Ethernet
adapter and the IP network. In the event of a local network fault, the cluster
will react as if the metadata server on which the fault occurred is down.
The master metadata server reforms the cluster, excluding the failed metadata
server. The metadata server itself will go into a wait state, and any filesets
assigned to that metadata server will no longer be available to clients.
- A network partition. A local network partition can occur if there is a
problem in the Ethernet network that causes two or more metadata servers to
lose communications with the master metadata server. The partition containing
the master metadata server will react as if the metadata servers in the other
partition are down. The metadata servers in the other partition will react
as if the master metadata server is down.