Thanks Andrew,<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Pacemaker has various options for how it behaves during a split-brain, but<br>
1) Its more desirable to avoid them in the first place<br>
2) None of the strategies are (yet) really suited to failing over from<br>
one physical location to another</blockquote><div> </div>i could not understand the second point. i am new to openais-pacemaker , but as far as i know we have lots of stoniths . for example if we have configured ilo properly then we can use riloe stonith and fence the node residing in other partiton. what is stopping us and why we are saying that we dont support cluster whose nodes spans over multiple site?? could you please explain it bit more. <br>
<br>and when u say "None of the strategies are (yet) really suited to failing over from<br>
one physical location to another" <br>does it apply to nodes who sapns over adjancent rooms also.??<br><br>sorry for bugging you too much. <br>Thanks a lot again for clearing my concepts.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="h5"><br>
<br>
>> That's why it is<br>
>> recommend to have a local cluster ( nodes sharing same rack).<br>
>><br>
>> am i right??<br>
>><br>
>> Thanks & Regards,<br>
>><br>
>> On Mon, Mar 2, 2009 at 12:47 PM, Andrew Beekhof <<a href="mailto:beekhof@gmail.com">beekhof@gmail.com</a>> wrote:<br>
>>><br>
>>> On Mon, Mar 2, 2009 at 04:27, Romi Verma <<a href="mailto:romi3rdfeb@gmail.com">romi3rdfeb@gmail.com</a>> wrote:<br>
>>> > Thanks Andrew and Lars,<br>
>>> > I would like to understand it bit more. , is there any distance<br>
>>> > parameter<br>
>>> > here? i mean to say suppose i have two nodes in one room and 1 node in<br>
>>> > adjacent room , cant i form three nodes openais/pacemaker cluster<br>
>>> > here.<br>
>>><br>
>>> of course.<br>
>>> i believe the point is that as the distance increases, so does the<br>
>>> number of switches/telcos involved and therefor the probability of a<br>
>>> comms failure is between the two sites is quite high.<br>
>>> as is the latency...<br>
>>><br>
>>> > i was under impression that as far as multicast ip works , nothing<br>
>>> > stops us<br>
>>> > in forming a cluster.<br>
>>> ><br>
>>> > Regrards,<br>
>>> ><br>
>>> ><br>
>>> > On Sat, Feb 28, 2009 at 12:04 AM, Lars Marowsky-Bree <<a href="mailto:lmb@suse.de">lmb@suse.de</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> On 2009-02-27T13:38:02, Romi Verma <<a href="mailto:romi3rdfeb@gmail.com">romi3rdfeb@gmail.com</a>> wrote:<br>
>>> >><br>
>>> >> > Thanks for reply Andrew,<br>
>>> >> > ok, then how openais-pacemaker cluster handles the cluster whose<br>
>>> >> > nodes<br>
>>> >> > span<br>
>>> >> > across multiple sites.<br>
>>> >><br>
>>> >> This is not currently handled.<br>
>>> >><br>
>>> >> But deploying a split-site setup with quorumd never worked either; it<br>
>>> >> is<br>
>>> >> not integrated with fencing, and it is impossible to build a working<br>
>>> >> split-site cluster with it. This was, I'm afraid to say, only a 40%<br>
>>> >> implementation of the solution even in heartbeat/CCM land.<br>
>>> >><br>
>>> >><br>
>>> >> Having proper split-site support is on the roadmap, as soon as the<br>
>>> >> openAIS integration stabilizes.<br>
>>> >><br>
>>> >><br>
>>> >> Regards,<br>
>>> >> Lars<br>
>>> >><br>
>>> >> --<br>
>>> >> Teamlead Kernel, SuSE Labs, Research and Development<br>
>>> >> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)<br>
>>> >> "Experience is the name everyone gives to their mistakes." -- Oscar<br>
>>> >> Wilde<br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> Pacemaker mailing list<br>
>>> >> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>>> >> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > Pacemaker mailing list<br>
>>> > <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>>> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>>> ><br>
>>> ><br>
>>><br>
>>> _______________________________________________<br>
>>> Pacemaker mailing list<br>
>>> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list<br>
> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
</div></div></blockquote></div><br>