RE: [Keepalived-devel] nopreempt not working with version 1.1.11

[Chris C. <cc...@al...>]

If I recall correctly...

If you set the initial state to MASTER than when it comes back up it will
take the IP without holding an election.  Ie., it will force the change.  
The "nopreempt" flag will stop elections, but will not stop a forced
change due to a MASTER state declaration.

If you set the initial state for both servers to BACKUP, but have one with
a higher priority than the other, "nopreempt" should prevent the one with
the higher priority from taking over via election.

In my case what I do is set both servers to initial state of BACKUP but I
have a preferred server that I wish to use when both machines have been up
for a while.  So instead of using "nopreempt" I use "preempt_delay 300"  
to cause an election to happen after 300 seconds of stability.

Chris

On Fri, 29 Apr 2005, Patrice Gamache wrote:
> No.. it is the master who have the higher ID 
> The backup have the lower
> 
> Pat Gamache
> 
> 
> -----Original Message-----
> From: Chris Caputo [mailto:cc...@al...] 
> Sent: 29 avril 2005 17:52
> To: Patrice Gamache
> Cc: kee...@li...
> Subject: Re: [Keepalived-devel] nopreempt not working with version 1.1.11
> 
> Did the server with the higher id have an initial state of BACKUP?
> 
> Chris
> 
> On Fri, 29 Apr 2005, Patrice Gamache wrote:
> > i put the nopreempt option to my backup server and when a server with a
> > higher id come online it become the master anyway.
> > 
> >  
> > 
> > Pat