Red Hat Bugzilla – Bug 209862
commit token data doesn't look correct sometimes when running mp5
Last modified: 2016-04-26 09:35:25 EDT
Description of problem:
this looks fishy from the logs:
Oct 6 19:38:35.056031 [TOTEM] entering RECOVERY state.
Oct 6 19:38:35.056083 [TOTEM] position  member 192.168.2.10:
Oct 6 19:38:35.056094 [TOTEM] previous ring seq 1125934283437147 rep 192.168.2.10
Oct 6 19:38:35.056102 [TOTEM] aru 28 high delivered 28 received flag 0
Oct 6 19:38:35.056111 [TOTEM] position  member 192.168.2.20:
Oct 6 19:38:35.056119 [TOTEM] previous ring seq 0 rep (null)
Oct 6 19:38:35.056126 [TOTEM] aru 0 high delivered 0 received flag 0
Oct 6 19:38:35.056134 [TOTEM] position  member 192.168.2.30:
Oct 6 19:38:35.056141 [TOTEM] previous ring seq 0 rep (null) Oct 6
19:38:35.056148 [TOTEM] aru 0 high delivered 0 received flag 0
Oct 6 19:38:35.056156 [TOTEM] position  member 192.168.2.31:
Oct 6 19:38:35.056163 [TOTEM] previous ring seq 0 rep (null)
Oct 6 19:38:35.056170 [TOTEM] aru 0 high delivered 0 received flag 0
Oct 6 19:38:35.056180 [TOTEM] Did not need to originate any messages in recovery.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run the mp5 test tool
The problem is that if a commit token is resent by a previous node, the next
node in the ring will also process the commit token again and send it on. This
causes tokens for forward nodes to be discarded by incorrect logic and the
COMMIT token to be lost in a properly formed ring. It also results in incorrect
EVS recovery which can result in segfaults of the protocol.
Created attachment 159910 [details]
patch to fix the problem.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.