My RHEL6 cluster just fell foul of the original problem so I can confirm
that this patch fixes it.
ACK :-)
Chrissie
On 09/08/14 00:06, jason wrote:
When there is no other activty on ring but only retransmition, and token
is in hold mode, the retransmition will become slow. More over, if the
retransmition is always fail but token rotation works well, then it takes
quite a lone time(fail_to_recv_const * token_hold = 2500 * 180ms = 450sec)
for the retransmit requester to meet the "FAILED TO RECEIVE" condition to
re-construct a new ring.
This problem can be solved by checking if retransmits are present before
going into hold. If a node is the retransmit requester or the resender, it
set my_token_held to 0 to speed up retransmition and omit further
unnecessary sending of token_hold_cancel signal.
Signed-off-by: Jason HU <huzhijiang@xxxxxxxxx>
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
