[Pacemaker] Multicast pitfalls? corosync [TOTEM ] Retransmit List:

Nikita Staroverov nsforth at gmail.com
Mon Feb 17 05:01:30 UTC 2014


14.02.2014 17:23, Beo Banks ?????:
> hi stefan,
> it seems that's more stable but after 2 minute the issue is back again.
> hopefully isn't a bug because it can reproduce it
> node2 sents only unicast at sequenz 256...
> node1
>
> omping 10.0.0.22 10.0.0.21
>
> 10.0.0.22 :unicast, seq=257, size=69 bytes, dist=0, time=0.666ms
>
> 10.0.0.22 : multicast, seq=257, size=69 bytes, dist=0, time=0.677ms
>
> 10.0.0.22 :unicast, seq=258, size=69 bytes, dist=0, time=0.600ms
>
> 10.0.0.22 : multicast, seq=258, size=69 bytes, dist=0, time=0.610ms
>
> 10.0.0.22 :unicast, seq=259, size=69 bytes, dist=0, time=0.693ms
>
> 10.0.0.22 : multicast, seq=259, size=69 bytes, dist=0, time=0.702ms
>
> 10.0.0.22 :unicast, seq=260, size=69 bytes, dist=0, time=0.674ms
>
> 10.0.0.22 : multicast, seq=260, size=69 bytes, dist=0, time=0.685ms
>
> 10.0.0.22 :unicast, seq=261, size=69 bytes, dist=0, time=0.658ms
>
> 10.0.0.22 : multicast, seq=261, size=69 bytes, dist=0, time=0.669ms
>
> 10.0.0.22 :unicast, seq=262, size=69 bytes, dist=0, time=0.834ms
>
> 10.0.0.22 : multicast, seq=262, size=69 bytes, dist=0, time=0.845ms
>
> 10.0.0.22 :unicast, seq=263, size=69 bytes, dist=0, time=0.666ms
>
> 10.0.0.22 : multicast, seq=263, size=69 bytes, dist=0, time=0.677ms
>
> 10.0.0.22 :unicast, seq=264, size=69 bytes, dist=0, time=0.675ms
>
> 10.0.0.22 : multicast, seq=264, size=69 bytes, dist=0, time=0.687ms
>
> 10.0.0.22 : waiting for response msg
>
> 10.0.0.22 : server told us to stop
>
>
Looks like you've got network congestion. You should run network 
delay/thoroughput tests, i think.
I see the same TOKEN RETRANSMIT messages, when my cluster nodes busy or so.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140217/66ddb54c/attachment.htm>


More information about the Pacemaker mailing list