[Pacemaker] Node recover causes resource to migrate

[Jacobo García]

Thanks for your answers.

Is it possible to configure corosync/pacemaker in this scenario so if a
node goes down instead of bringing the node back I can build a new one and
add it to the cluster? Building new nodes is almost "free" for me. Also,
what's the difference between bringing a new node from scratch or starting
the node that goes down? How is this treated in an a normal scenario? (IE
you want to add a third node to a cluster).

Side note, I have decided not to use amazon VPC for several reasons, it can
be summarized in: too much hassle to set up even on the simplest
configuration that would involve an HA solution for the router between the
two networks.

Jacobo García López de Araujo
http://thebourbaki.com | http://twitter.com/clapkent


On Wed, Jul 24, 2013 at 11:26 AM, Lars Marowsky-Bree <lmb at suse.com> wrote:

> On 2013-07-24T09:00:23, Andrew Beekhof <andrew at beekhof.net> wrote:
>
> > > 4. Node A is back with a different internal ip address.
> >
> > This is your basic problem.
> >
> > I don't believe there is any cluster software that is designed to
> support this sort of scenario.
> > Even at the corosync level, it has no knowledge that this is the same
> machine that left.
>
> Statically assigned nodeids?
>
>
>
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
> Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130724/713f806e/attachment-0003.html>