You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2018/02/01 22:52:17 UTC
[jira] [Closed] (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 ]
Swapnil Bawaskar closed GEODE-3780.
-----------------------------------
> 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
> Priority: Major
> Fix For: 1.4.0
>
>
> 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)