[ClusterLabs] One Failed Resource = Failover the Cluster?

Antony Stone Antony.Stone at ha.open.source.it
Mon Jun 7 16:00:15 EDT 2021

On Monday 07 June 2021 at 21:49:45, Eric Robinson wrote:

> > -----Original Message-----
> > From: kgaillot at redhat.com <kgaillot at redhat.com>
> > Sent: Monday, June 7, 2021 2:39 PM
> > To: Strahil Nikolov <hunter86_bg at yahoo.com>; Cluster Labs - All topics
> > related to open-source clustering welcomed <users at clusterlabs.org>; Eric
> > Robinson <eric.robinson at psmnv.com>
> > Subject: Re: [ClusterLabs] One Failed Resource = Failover the Cluster?
> > 
> > By default, dependent resources in a colocation will affect the placement
> > of the resources they depend on.
> > 
> > In this case, if one of the mysql instances fails and meets its migration
> > threshold, all of the resources will move to another node, to maximize
> > the chance of all of them being able to run.
> Which is what I don't want to happen. I only want the cluster to failover
> if one of the lower dependencies fails (drbd or filesystem). If one of the
> MySQL instances fails, I do not want the cluster to move everything for
> the sake of that one resource. That's like a teacher relocating all the
> students in the classroom to a new classroom because one of then lost his
> pencil.

Okay, so let's focus on what you *do* want to happen.

One MySQL instance fails.  Nothing else does.

What do you want next?

 - Cluster continues with a failed MySQL resource?

 - MySQL resource moves to another node but no other resources move?

 - something else I can't really imagine right now?

I'm sure that if you can define what you want the cluster to do in this 
situation (MySQL fails, all else continues okay), someone here can help you 
explain that to pacemaker.


This email was created using 100% recycled electrons.

                                                   Please reply to the list;
                                                         please *don't* CC me.

More information about the Users mailing list