On 1/23/07, home_king <[EMAIL PROTECTED]> wrote:
Hi, Andrew.
I have a question about the election.
Why the layer3, crm modules launches another election, while the
layer2, the CCM, already in charge of election & join protocol, which
even forms a memebership list sorted by bornon & UUID? It seems redundant.
as you correctly point out, the ccm tells us the set of fully
connected nodes and who the oldest one is.
however:
* these are not the only factors that go into the election
* its likely that we wont be running on top of the ccm forever
It just safely probes the per activity of layer3 modules, I think. Any
functions else? Of course, join protocol in CRM initializes CIB, which
guides CIB to do a full-sync-job.
The join protocol does more than a full-sync:
* checks peers conform to various criteria before being admitted
* finds the node with the "best" configuration
* gathers the latest resource status from each node and merges it together
But why implement the join protocol
in CIB, and this seems more natively.
You mean why _not_ right?
Because the cib is intended to be as stupid as possible to make it
resilient to version changes. It would probably also require the CIB
to also have some sort of election.
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
