>>> Ken Gaillot schrieb am 09.09.2019 um 17:14 in
Nachricht
<9e51c562c74e52c3b9e5f85576210bf83144fae7.ca...@redhat.com>:
> On Mon, 2019‑09‑09 at 11:06 +0200, Ulrich Windl wrote:
>> Hi!
>>
>> In recent pacemaker I see that last‑lrm‑refresh is included in the
>> CIB config (crm_config/cluster_prope
On Mon, 2019-09-09 at 14:21 +0200, wf...@niif.hu wrote:
> Andrei Borzenkov writes:
>
> > 04.09.2019 0:27, wf...@niif.hu пишет:
> >
> > > Jeevan Patnaik writes:
> > >
> > > > [16187] node1 corosyncwarning [MAIN ] Corosync main process
> > > > was not
> > > > scheduled for 2889.8477 ms (thresho
On Mon, 2019-09-09 at 11:06 +0200, Ulrich Windl wrote:
> Hi!
>
> In recent pacemaker I see that last-lrm-refresh is included in the
> CIB config (crm_config/cluster_property_set), so CIBs are "different"
> when they are actually the same.
>
> Example diff:
> - name="last-lrm-refresh" value=
Jeevan Patnaik writes:
> writes:
>
>> Jeevan Patnaik writes:
>>
>>> [16187] node1 corosyncwarning [MAIN ] Corosync main process was not
>>> scheduled for 2889.8477 ms (threshold is 800. ms). Consider token
>>> timeout increase.
>>> [...]
>>> 2. How to fix this? We have not much load on the
Andrei Borzenkov writes:
> 04.09.2019 0:27, wf...@niif.hu пишет:
>
>> Jeevan Patnaik writes:
>>
>>> [16187] node1 corosyncwarning [MAIN ] Corosync main process was not
>>> scheduled for 2889.8477 ms (threshold is 800. ms). Consider token
>>> timeout increase.
>>> [...]
>>> 2. How to fix th
Hi!
In recent pacemaker I see that last-lrm-refresh is included in the CIB config
(crm_config/cluster_property_set), so CIBs are "different" when they are
actually the same.
Example diff:
-
+
I don't see a reason for having that. Can someone explain?
Regards,
Ulrich
___