[ClusterLabs] Continuous membership events in Corosync

[Prasad Nagaraj]

Hi - I am trying to set up a 3 node cluster. I have got the corosync up and
running on all the nodes and all nodes have joined the cluster. However, in
the corosync logs, I am seeing continuous and repeated messages about
membership events on rings. It comes every 12 seconds on all nodes.

Here is a sample:

May 03 10:46:29 corosync [pcmk  ] notice: pcmk_peer_update: Transitional
membership event on ring 2264: memb=3, new=0, lost=0
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: memb:
vme6c794899e 83891884
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: memb:
vmc9d15655fe 151000748
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: memb:
vm5e42438470 184555180
May 03 10:46:29 corosync [pcmk  ] notice: pcmk_peer_update: Stable
membership event on ring 2264: memb=3, new=0, lost=0
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vme6c794899e 83891884
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vmc9d15655fe 151000748
May 03 10:46:29 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vm5e42438470 184555180
May 03 10:46:29 corosync [TOTEM ] A processor joined or left the membership
and a new membership was formed.
May 03 10:46:29 corosync [CPG   ] chosen downlist: sender r(0)
ip(172.22.0.5) ; members(old:3 left:0)
May 03 10:46:29 corosync [MAIN  ] Completed service synchronization, ready
to provide service.

May 03 10:46:41 corosync [pcmk  ] notice: pcmk_peer_update: Transitional
membership event on ring 2268: memb=3, new=0, lost=0
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: memb:
vme6c794899e 83891884
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: memb:
vmc9d15655fe 151000748
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: memb:
vm5e42438470 184555180
May 03 10:46:41 corosync [pcmk  ] notice: pcmk_peer_update: Stable
membership event on ring 2268: memb=3, new=0, lost=0
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vme6c794899e 83891884
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vmc9d15655fe 151000748
May 03 10:46:41 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vm5e42438470 184555180
May 03 10:46:41 corosync [TOTEM ] A processor joined or left the membership
and a new membership was formed.
May 03 10:46:41 corosync [CPG   ] chosen downlist: sender r(0)
ip(172.22.0.5) ; members(old:3 left:0)
May 03 10:46:41 corosync [MAIN  ] Completed service synchronization, ready
to provide service.

May 03 10:46:54 corosync [pcmk  ] notice: pcmk_peer_update: Transitional
membership event on ring 2272: memb=3, new=0, lost=0
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: memb:
vme6c794899e 83891884
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: memb:
vmc9d15655fe 151000748
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: memb:
vm5e42438470 184555180
May 03 10:46:54 corosync [pcmk  ] notice: pcmk_peer_update: Stable
membership event on ring 2272: memb=3, new=0, lost=0
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vme6c794899e 83891884
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vmc9d15655fe 151000748
May 03 10:46:54 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vm5e42438470 184555180
May 03 10:46:54 corosync [TOTEM ] A processor joined or left the membership
and a new membership was formed.
May 03 10:46:54 corosync [CPG   ] chosen downlist: sender r(0)
ip(172.22.0.5) ; members(old:3 left:0)
May 03 10:46:54 corosync [MAIN  ] Completed service synchronization, ready
to provide service.

May 03 10:47:06 corosync [pcmk  ] notice: pcmk_peer_update: Transitional
membership event on ring 2276: memb=3, new=0, lost=0
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: memb:
vme6c794899e 83891884
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: memb:
vmc9d15655fe 151000748
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: memb:
vm5e42438470 184555180
May 03 10:47:06 corosync [pcmk  ] notice: pcmk_peer_update: Stable
membership event on ring 2276: memb=3, new=0, lost=0
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vme6c794899e 83891884
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vmc9d15655fe 151000748
May 03 10:47:06 corosync [pcmk  ] info: pcmk_peer_update: MEMB:
vm5e42438470 184555180
May 03 10:47:06 corosync [TOTEM ] A processor joined or left the membership
and a new membership was formed.
May 03 10:47:06 corosync [CPG   ] chosen downlist: sender r(0)
ip(172.22.0.5) ; members(old:3 left:0)
May 03 10:47:06 corosync [MAIN  ] Completed service synchronization, ready
to provide service.

My corosync version is :corosync-1.4.7-5.el6.x86_64

my corosync.conf is :
compatibility: whitetank
totem {
    version: 2
    secauth: off
    threads: 0
    interface {
    member {
            memberaddr: 172.22.0.5
        }
member {
            memberaddr: 172.22.0.9
        }
member {
            memberaddr: 172.22.0.11
        }

    bindnetaddr: 172.22.0.5

    ringnumber: 0
    mcastport: 5405
    ttl: 1
    }
    transport: udpu
    token: 10000
    token_retransmits_before_loss_const: 10
}

logging {
    fileline: off
    to_stderr: yes
    to_logfile: yes
    to_syslog: no
    logfile: /var/log/cluster/corosync.log
    timestamp: on
    logger_subsys {
    subsys: AMF
    debug: off
    }
}
service {
    name: pacemaker
    ver: 1
}
amf {
    mode: disabled
}

Appreciate any pointers on why this is happening and what is the solution.

Thanks
Prasad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180503/2d90f040/attachment.html>