Hi Ken - Thanks for you response.
We do have seen messages in other cases like
corosync [MAIN ] Corosync main process was not scheduled for 17314.4746 ms
(threshold is 8000. ms). Consider token timeout increase.
corosync [TOTEM ] A processor failed, forming new configuration.
Is this the ind
On Sun, 2018-08-19 at 17:35 +0530, Prasad Nagaraj wrote:
> Hi:
>
> One of these days, I saw a spurious node loss on my 3-node corosync
> cluster with following logged in the corosync.log of one of the
> nodes.
>
> Aug 18 12:40:25 corosync [pcmk ] notice: pcmk_peer_update:
> Transitional membersh
Hi:
One of these days, I saw a spurious node loss on my 3-node corosync cluster
with following logged in the corosync.log of one of the nodes.
Aug 18 12:40:25 corosync [pcmk ] notice: pcmk_peer_update: Transitional
membership event on ring 32: memb=2, new=0, lost=1
Aug 18 12:40:25 corosync [pcmk
