On 2021-06-08 5:24 p.m., kgail...@redhat.com wrote:
> Hi all,
>
> Pacemaker 2.1.0 has officially been released, with source code
> available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0
>
> Highlights include OCF Resource Agent API 1.1 compatibility,
>
> -Original Message-
> From: Users On Behalf Of Tomas Jelinek
> Sent: Tuesday, June 1, 2021 3:40 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Quorum when reducing cluster from 3 nodes to 2
> nodes
>
> Hi Robert,
>
> Your corosync.conf looks fine to me, node app3 has been
Hi all,
Pacemaker 2.1.0 has officially been released, with source code
available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.1.0
Highlights include OCF Resource Agent API 1.1 compatibility,
noncritical resources, and new build-time options. The Pacemaker
documentation
Hello,
Yes, the promoted role of one of the dbs will failover to a node that is not using the virtual IP address. However, neither the db resources nor the virtual IP resources will follow the db that failed over, hence we end up in a state where the dbs are located on separate nodes and the
> -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:
> >
> > Which is what I don't want
