Digimer <[email protected]> writes: > This generally happens if the network is slow or congested. It is > corosync saying it needs to resend some messages. It is not uncommon > for it to happen now and then, but that is a fairly large amount of > retransmits.
Thanks for the explanation.
> Is your network slow or saturated often? It might be that the traffic
> from the join is enough to push a congested network to the edge.
Not really:
- two physical hosts with:
+ one 1Gb/s network card for OS (corosync network)
+ three 1Gb/s network cards in LACP bonding included in an Open
vSwitch
- one physical host with:
+ one 10Gb/s network card for the OS (corosync network)
+ three 10Gb/s network cards in LACP bonding included in an Open
vSwitch
- one KVM guest (quorum node) with:
+ one virtio card (corosync network)
- one KVM guest with:
+ one virtio card for service (OpenNebula web frontend)
+ one virtio card for corosync communications
With tcpdump I can see packets flying around on all nodes, but it looks
like there is something with my two cards KVM guest, when I start
pacemaker on it I begin to see Retransmit messages in other nodes logs.
Is there a may to know which nodes is responsible of the resend of
theses messages?
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
signature.asc
Description: PGP signature
_______________________________________________ Pacemaker mailing list: [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
