[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] cluster request failed: Host is down

On Fri, Nov 16, 2012 at 04:15:27PM +0100, Zdenek Kabelac wrote:
> Cluster with just 1 node is not a cluster (no quorum)

It is a cluster, in a degraded state. An expected situation for two-node

I use the corosync stack, which provides the quorum information (there
are special settings to provide quorum on failed two-node cluster) and I
have fencing configured to enforce the quorum. Every other piece of the
cluster trust the quorum information from corosync.

> So you may either drop locking --config 'global {locking_type = 0}'

That misses the point.

> or fix the dropped node.  Since you are admin of the system you
> know what to do - 

Yes. Make sure the cluster has proper quorum and fencing configured.

The cluster is supposed to provide high availability – which means
a graceful fail-over in case a node fails.

> system itself unfortunately cannot determine,
> whether the node A is master or node B is master (both could
> be alive, just Internet connection between them could be failing).

That is true if there is no proper fencing configured. But I have
working fencing. If there is no communication with the other node 
(due to hardware or software problem) its power is turned off. It is
known that the other node is not 'master' at that moment.

As DLM already made sure the other node is not running (it would lock up
on any lock operation otherwise) I see no reason for CLVMD not to trust
DLM (that lock is provided to all lock-space members) and Corosync (that
we have quorum).

And the message says 'Host is down', not 'no quorum' or anything which
would suggest that is a problem.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]