Hi!

but like with CPU affinity there should be no needless change of the DC. I also 
wondered why after each configuration change the DC is newly elected (it seems).

Regards,
Ulrich

>>> Andrew Beekhof <[email protected]> schrieb am 05.02.2012 um 23:48 in 
>>> Nachricht
<caedlwg1yc2sug+q4mqko_gjdypnd-o0bkhzhmbpyh3ovjma...@mail.gmail.com>:
> The location of the DC is an internal detail which you shouldn't care about.
> Why do you want to be able to predetermine its location?
> 
> On Sun, Feb 5, 2012 at 1:53 PM, Mayank <[email protected]> wrote:
> > Hello all,
> >
> >   I'm using pacemaker to manage our some of resources including Virtual IP.
> > It is working well in case of failover.  Now we've to execute some our
> > policies before selecting DC during split-brain resolution. Still I'm unable
> > to figure out on what basis pacemaker selects DC after split-brain
> > resolution. If I've 2 node setup, some time it selects node-1 other times it
> > selects node-2. We've out RA which is forced to run on the node which is DC.
> > Just because of this un-predicable behavior of DC selection, we want to
> > execute some of our policies before selecting DC. Is there any way to do 
> so?
> >
> >
> >
> > Mayank Mittal
> >
> > _______________________________________________
> > 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 
> 

 
 

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to