[GEODE-3780] suspected member is never watched again after passing final check

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: membership
• Labels: pull-request-available
• Assignee: Bruce J Schuchardt
• Reporter: Bruce J Schuchardt
• Created: 06/Oct/17 18:19
• Updated: 30/Dec/19 18:50
• Resolved: 14/Oct/19 20:35

Description

In a network-down test we saw a node on the losing side of the network partition perform final checks on members on the winning side. One of the final checks mysteriously succeeded

[info 2017/09/17 12:24:45.552 PDT gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 <Geode Failure Detection thread 4> tid=0x128] Final check failed but detected recent message traffic for suspect member 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135)<v2>:1026
[info 2017/09/17 12:24:45.552 PDT gemfire1_rs-FullRegression-2017-09-15-21-00-35-client-10_8941 <Geode Failure Detection thread 4> tid=0x128] Final check passed for suspect member 10.32.109.252(gemfire3_rs-FullRegression-2017-09-15-21-00-35-client-16_6135:6135)<v2>:1026

After this the suspected member was never checked again and the losing side failed to shut down.

Issue Links

• links to: GitHub Pull Request #2309
• links to: GitHub Pull Request #2380
• links to: GitHub Pull Request #3917
• links to: GitHub Pull Request #3949
• links to: GitHub Pull Request #4124