Re: [ClusterLabs] What Does the Monitor Action of the IPaddr2 RA Actually Do?

On 02.06.2021 23:38, Eric Robinson wrote: >> -Original Message- >> From: Users On Behalf Of Andrei >> Borzenkov >> Sent: Tuesday, June 1, 2021 1:14 PM >> To: users@clusterlabs.org >> Subject: Re: [ClusterLabs] What Does the Monitor Action of the IPaddr2 RA >> Actually Do? >> >> On

Re: [ClusterLabs] Cluster Stopped, No Messages?

> -Original Message- > From: Users On Behalf Of Andrei > Borzenkov > Sent: Tuesday, June 1, 2021 12:52 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Cluster Stopped, No Messages? > > On 01.06.2021 19:21, Eric Robinson wrote: > > > >> -Original Message- > >> From:

Re: [ClusterLabs] What Does the Monitor Action of the IPaddr2 RA Actually Do?

> -Original Message- > From: Users On Behalf Of Andrei > Borzenkov > Sent: Tuesday, June 1, 2021 1:14 PM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] What Does the Monitor Action of the IPaddr2 RA > Actually Do? > > On 01.06.2021 19:50, Eric Robinson wrote: > > This is related

[ClusterLabs] Pacemaker Cluster help

Is there a way to have pacemaker resource groups failover if all floating IP resources are unavailable? I want to have multiple floating IPs in a resource group that will only failover if all IPs cannot work. Each floating IP is on a different subnet and can be used by the application I

[ClusterLabs] Corosync Membership Reforms randomly.

Hi , I am using Pacemaker/Corosync on RHEL 7.4 where facing the below issue randomly. The corosync reforms the membership randomly even though the service was not restarted. I could observe the below log in the messages file before corosync reforms the membership, Log: May 9 18:02:15

[ClusterLabs] Antw: [EXT] Pacemaker Cluster help

>>> Nathan Mazarelo schrieb am 02.06.2021 um 15:12 >>> in Nachricht <1283884976.2711546.1622639579...@mail.yahoo.com>: > Is there a way to have pacemaker resource groups failover if all floating IP > resources are unavailable? > > I want to have multiple floating IPs in a resource group

Re: [ClusterLabs] Antw: Hanging OCFS2 Filesystem any one else?

Hi Ulrich, The hang problem looks like a fix (90bd070aae6c4fb5d302f9c4b9c88be60c8197ec ocfs2: fix deadlock between setattr and dio_end_io_write), but it is not 100% sure. If possible, could you help to report a bug to SUSE, then we can work on that further. Thanks Gang

[ClusterLabs] Antw: [EXT] Re: Antw: Hanging OCFS2 Filesystem any one else?

>>> Gang He schrieb am 02.06.2021 um 08:34 in Nachricht > Hi Ulrich, > > The hang problem looks like a fix (90bd070aae6c4fb5d302f9c4b9c88be60c8197ec > ocfs2: fix deadlock between setattr and dio_end_io_write), but it is not 100% > sure. > If possible, could you help to report a bug to SUSE,

Re: [ClusterLabs] Antw: [EXT] no-quorum-policy=stop never executed, pacemaker stuck in election/integration, corosync running in "new membership" cycles with itself

lge> > I would have expected corosync to come back with a "stable lge> > non‑quorate membership" of just itself within a very short lge> > period of time, and pacemaker winning the lge> > "election"/"integration" with just itself, and then trying lge> > to call "stop" on everything it knows about.