[
https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597595#comment-16597595
]
ASF subversion and git services commented on GEODE-3780:
--------------------------------------------------------
Commit 9ee8cbfe3000df4db87a7388d0123aa40e42b7ec in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9ee8cbf ]
GEODE-3780 member is not considered suspect after failing final check
Ensure that a member is in the suspects collection after it fails a
final check. This allows processSuspectMessage to know if it should
perform the duty of a membership-coordinator and initiate final
checks based on Suspect messages.
I've also done a little bit of refactoring in processSuspectMessage and
have removed commented-out code.
This closes #2380
> suspected member is never watched again after passing final check
> -----------------------------------------------------------------
>
> Key: GEODE-3780
> URL: https://issues.apache.org/jira/browse/GEODE-3780
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
