>>> Jan Pokorný schrieb am 29.04.2019 um 17:22 in
Nachricht
<20190429152200.ga19...@redhat.com>:
> On 29/04/19 14:58 +0200, Jan Pokorný wrote:
>> On 29/04/19 08:20 +0200, Ulrich Windl wrote:
>> Jan Pokorný schrieb am 25.04.2019 um 18:49
>> in Nachricht
As soon as majority of nodes are stopped, the remaining nodes are out of
quorum and watchdog reboot kicks in.
What is the correct procedure to ensure nodes are stopped in clean way?
Short of disabling stonith-watchdog-timeout before stopping cluster ...
29.04.2019 14:32, Jan Friesse пишет:
> Andrei,
>
>> I setup qdevice in openSUSE Tumbleweed and while it works as expected I
>
> Is it corosync-qdevice or corosync-qnetd daemon?
>
corosync-qdevice
>> cannot stop it - it always results in timeout and service finally gets
>> killed by systemd.
29.04.2019 18:05, Ken Gaillot пишет:
>>
>>> Why does not it check OCF_RESKEY_CRM_meta_notify?
>>
>> I was just not aware of this env variable. Sadly, it is not
>> documented
>> anywhere :(
>
> It's not a Pacemaker-created value like the other notify variables --
> all user-specified
On Sat, 2019-04-27 at 10:27 +0300, Andrei Borzenkov wrote:
> Documentation says for clone resources OCF_RESOURCE_INSTANCE contains
> primitive qualified by instance number, like primitive:1.
That is pacemaker's practice (inherited from heartbeat).
The OCF standard itself says the variable
On 29/04/19 14:58 +0200, Jan Pokorný wrote:
> On 29/04/19 08:20 +0200, Ulrich Windl wrote:
> Jan Pokorný schrieb am 25.04.2019 um 18:49
> in Nachricht <20190425164946.gf23...@redhat.com>:
>>> I think the prime and foremost use case is that half of the actual
>>> pacemaker daemons run as
On Sun, 2019-04-28 at 00:27 +0200, Jehan-Guillaume de Rorthais wrote:
> On Sat, 27 Apr 2019 09:15:29 +0300
> Andrei Borzenkov wrote:
>
> > 27.04.2019 1:04, Danka Ivanović пишет:
> > > Hi, here is a complete cluster configuration:
> > >
> > > node 1: master
> > > node 2: secondary
> > >
On 29/04/19 08:20 +0200, Ulrich Windl wrote:
Jan Pokorný schrieb am 25.04.2019 um 18:49
in Nachricht <20190425164946.gf23...@redhat.com>:
>> On 24/04/19 09:32 ‑0500, Ken Gaillot wrote:
>>> On Wed, 2019‑04‑24 at 16:08 +0200, wf...@niif.hu wrote:
Make install creates
Andrei,
I setup qdevice in openSUSE Tumbleweed and while it works as expected I
Is it corosync-qdevice or corosync-qnetd daemon?
cannot stop it - it always results in timeout and service finally gets
killed by systemd.
Is it a known issue? TW is having quite up-to-date versions, it usually
>>> Jan Pokorný schrieb am 25.04.2019 um 18:49 in
Nachricht
<20190425164946.gf23...@redhat.com>:
> On 24/04/19 09:32 ‑0500, Ken Gaillot wrote:
>> On Wed, 2019‑04‑24 at 16:08 +0200, wf...@niif.hu wrote:
>>> Make install creates /var/log/pacemaker with mode 0770, owned by
>>> hacluster:haclient.
10 matches
Mail list logo
