On Thu, 19 Sep 2013, Fabio M. Di Nitto wrote:
On 09/19/2013 12:47 AM, David Lang wrote:
I'm trying to get a cluster up and running without using multicast, I've
made my cluster.conf be the following, but the systems are still sending
to the multicast address and not seeing each other as a result.
Is there something that I did wrong in creating the cman segment of the
file? unforutunantly the cluster.conf man page just referrs to the
corosync.conf man page, but the two files use different config styles.
If not, what else do I need to do to disable multicast and just use udpu?
<cman two_node="1" expected_votes="1">
<totem vsftype="none" token="5000"
token_retransmits_before_loss_const="10" join="60" consensus="4800"
rrp_mode="none" transport="udpu">
<interface ringnumber="0" bindnetaddr="10.1.18.0" mcastport="5405"
ttl="1" >
<member memberaddr="10.1.18.177" />
<member memberaddr="10.1.18.178" />
</interface>
</totem>
</cman>
You don't need all of that...
<cman two_node="1" expected_votes="1" transport="udpu"/>
There is no need to specify anything else. memberaddresses et all will
be determined by the node names.
Ok, that solves my problem in most cases (8 of the 10 clusters I'm configuring
right now)
in the other two clusters, I will actually have 4 boxes per cluster, and I want
a resource to run on only one of the four. I don't care which one, and split
brain is not a major problem (no shared storage)
is it enough to just specify 4 nodes? (leaving "two_node=1" in place), do I just
remove the two_node attribute? or does this get really ugly?
An example of one of these two clusters.
Log alerting engines. All boxes in the cluster will receive copies of all logs,
and process them in parallel. I want to have only one of the four boxes be the
'active' box that sends out alerts (my alert scripts can test for the presense
of a resource on the local box)
The four boxes are actually two pairs in each of two datacenters. There is not
going to be a quarum because neither half would have enough systems to form one.
In the common split brain case (two clusters of two boxes because of datacenter
crosslink outage), alerts will be generated from both halves. This is a very
tolerable 'worst case' (and may even be the right thing, since for the duration
of the split, each one may be seeing logs that the other doesn't see, the
alerting path may follow different network connectivity so alerts may get
through even if ring packets don't)
David Lang
_______________________________________________
Openais mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/openais
