You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (Jira)" <ji...@apache.org> on 2019/08/20 15:30:00 UTC
[jira] [Updated] (GEODE-3780) suspected member is never watched
again after passing final check
[ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt updated GEODE-3780:
------------------------------------
Fix Version/s: (was: 1.11.0)
1.10.0
> 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.10.0
>
> Time Spent: 2.5h
> 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
(v8.3.2#803003)