Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-08 Thread Eric Robinson
> -Original Message- > From: Users On Behalf Of Andrei > Borzenkov > Sent: Tuesday, June 8, 2021 12:20 AM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] One Failed Resource = Failover the Cluster? > > On 07.06.2021 22:49, Eric Robinson wrote: > >

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread Andrei Borzenkov
On 07.06.2021 22:49, Eric Robinson wrote: > > 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 r

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread Antony Stone
> > Robinson > > 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 instance

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread Eric Robinson
> -Original Message- > From: kgail...@redhat.com > Sent: Monday, June 7, 2021 2:39 PM > To: Strahil Nikolov ; Cluster Labs - All topics > related to open-source clustering welcomed ; Eric > Robinson > Subject: Re: [ClusterLabs] One Failed Resource = Failover the Clus

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread kgaillot
> To: Cluster Labs - All topics related to open-source clustering > > welcomed > > > > > > Subject: Re: [ClusterLabs] One Failed Resource = Failover the > > Cluster? > > > > > > On Fri, 2021-06-04 at 19:10 +, Eric Robinson wrote: > >

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread kgaillot
d > > > > Subject: Re: [ClusterLabs] One Failed Resource = Failover the > > Cluster? > > > > On Fri, 2021-06-04 at 19:10 +, Eric Robinson wrote: > > > Sometimes it seems like Pacemaker fails over an entire cluster > > > when > > > on

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-07 Thread Eric Robinson
Not even if a mysql resource fails to stop? From: Strahil Nikolov Sent: Sunday, June 6, 2021 3:27 AM To: Cluster Labs - All topics related to open-source clustering welcomed ; Eric Robinson Subject: Re: [ClusterLabs] One Failed Resource = Failover the Cluster? Based on the constraint rules

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-06 Thread Strahil Nikolov
wrote: > -Original Message- > From: Users On Behalf Of > kgail...@redhat.com > Sent: Friday, June 4, 2021 4:49 PM > To: Cluster Labs - All topics related to open-source clustering welcomed > > Subject: Re: [ClusterLabs] One Failed Resource = Failover the Cluster? >

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-05 Thread Eric Robinson
> -Original Message- > From: Users On Behalf Of > kgail...@redhat.com > Sent: Friday, June 4, 2021 4:49 PM > To: Cluster Labs - All topics related to open-source clustering welcomed > > Subject: Re: [ClusterLabs] One Failed Resource = Failover the Cluster? > >

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-04 Thread Strahil Nikolov
It shouldn't relocate or affect any other resource,as long as the stop succeeds.If the stop operation times out or fails -> fencing kicks in. Best Regards,Strahil Nikolov___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users

Re: [ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-04 Thread kgaillot
On Fri, 2021-06-04 at 19:10 +, Eric Robinson wrote: > Sometimes it seems like Pacemaker fails over an entire cluster when > only one resource has failed, even though no other resources are > dependent on it. Is that expected behavior? > > For example, suppose I have the following colocation c

[ClusterLabs] One Failed Resource = Failover the Cluster?

2021-06-04 Thread Eric Robinson
Sometimes it seems like Pacemaker fails over an entire cluster when only one resource has failed, even though no other resources are dependent on it. Is that expected behavior? For example, suppose I have the following colocation constraints... filesystem with drbd master vip with filesystem my