On Nov 9, 2007, at 4:34 PM, Sebastian Reitenbach wrote:
Hi,
I did some tests with a two node cluster and a third one running a
quorumd.
I started the quorumd, and then the two cluster nodes.
The one that became DC, started to communicate with the remote
quorumd.
The CRM (and thus the "DC") doesn't know anything about quorumd
I believe this is purely the domain of the CCM and I've no idea how
that works :-)
We just consume membership data from it...
So anyway, my point is that the fact that a node is the DC is
irrelevant when it comes to quorumd.
I killed the DC, saw the other becoming DC, and start communicating
to the remote quorumd, all fine, cluster still with quorum.
Then I killed the quorumd itself, the DC recognized, and started to
stop
all resource, because of the quorum_policy, as it lost quorum.
Then I restarted the quorumd again, but the DC, still without quorum,
did not tried to communicate to the quorumd again.
I'd expect the still living DC to try to contact the quorumd, in
case it
comes back.
If there is a good reason, why the DC is not trying to reconnect to
the
remote quorumd I'd really like to get enlightened from someone who
knows.
kind regards
Sebastian
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
