On Wed, 2019-10-23 at 15:53 +0300, Andrei Borzenkov wrote:
> 23.10.2019 13:35, Ulrich Windl пишет:
> > Hi!
> >
> > In SLES12 SP4 I'm kind of annoyed due to repeating messages
> > "unpack_config:Watchdog will be used via SBD if fencing is
> > required".
It is annoying, but it's a side effect
ClusterLabs is happy to announce fence-agents v4.5.2, which is a
bugfix release for v4.5.1.
The source code is available at:
https://github.com/ClusterLabs/fence-agents/releases/tag/v4.5.2
The most significant enhancements in this release are:
- bugfixes and enhancements:
- fence_compute:
23.10.2019 13:35, Ulrich Windl пишет:
> Hi!
>
> In SLES12 SP4 I'm kind of annoyed due to repeating messages "unpack_config:
> Watchdog will be used via SBD if fencing is required".
>
> While examining another problem, I found this sequence:
> * Some unrelated resource was moved (migrated)
>
Hi!
In SLES12 SP4 I'm kind of annoyed due to repeating messages "unpack_config:
Watchdog will be used via SBD if fencing is required".
While examining another problem, I found this sequence:
* Some unrelated resource was moved (migrated)
* stonith-ng: info: update_cib_stonith_devices_v2:
21.10.2019 9:39, Ulrich Windl пишет:
"Dileep V Nair" schrieb am 20.10.2019 um 17:54 in
> Nachricht
>
> m>:
>
>> Hi,
>>
>> I am confused about the best way to stop pacemaker on both nodes of a
>> two node cluster. The options I know of are
>> 1. Put the cluster in Maintenance Mode,
Hi Christine,
Thank for your explanation.
Originally, there is concurrent fence feature in Pacemaker, you clear my doubt
:-)
Thanks
Gang
> -Original Message-
> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of christine
> caulfield
> Sent: 2019年10月23日 15:09
> To:
ClusterLabs is happy to announce resource-agents v4.4.0.
Source code is available at:
https://github.com/ClusterLabs/resource-agents/releases/tag/v4.4.0
The most significant enhancements in this release are:
- bugfixes and enhancements:
- NodeUtilization: fix Xen detection and improve logging
On 22/10/2019 07:15, Gang He wrote:
Hi List,
I remember that master node has the full copy for one DLM lock resource and the
other nodes have their own lock status,
then if one node is failed(or fenced), the DLM lock status can be recovered
from the remained node quickly.
My question is,
if
