geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lynn Hughes-Godfrey (Jira)" <j...@apache.org>
Subject [jira] [Reopened] (GEODE-3780) suspected member is never watched again after passing final check
Date Wed, 25 Sep 2019 21:35:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lynn Hughes-Godfrey reopened GEODE-3780:
----------------------------------------

Reopen as we are still seeing members hanging vs. being forcefully disconnected.

While I am not seeing Final checks in the logs, we see the messages below ... and then nothing
for nearly 3 minutes, as if we've stopped checking.
{noformat}
[info 2019/09/24 10:05:17.646 PDT <unicast receiver,rs-FullRegression24161617a3i3large-hydra-client-57-40823>
tid=0x27] received suspect message from 10.32.108.190(bridgep1_host1_13463:13463)<v4>:41002
for 10.32.111.26(bridgep2_host2_12641:12641)<v2>:41002: Unable to send messages to this
member via JGroups

[info 2019/09/24 10:05:17.646 PDT <unicast receiver,rs-FullRegression24161617a3i3large-hydra-client-57-40823>
tid=0x27] received suspect message from 10.32.108.190(bridgep1_host1_13463:13463)<v4>:41002
for 10.32.111.26(bridgep2_host2_12630:12630)<v3>:41003: Unable to send messages to this
member via JGroups

[info 2019/09/24 10:05:17.647 PDT <unicast receiver,rs-FullRegression24161617a3i3large-hydra-client-57-40823>
tid=0x27] received suspect message from 10.32.108.190(bridgep1_host1_13463:13463)<v4>:41002
for 10.32.111.26(locatorp2_host2_12681:12681:locator)<ec><v0>:41000: Unable to
send messages to this member via JGroups

[info 2019/09/24 10:05:18.284 PDT <P2P message reader for 10.32.111.26(locatorp2_host2_12681:12681:locator)<ec><v0>:41000
shared ordered uid=4 port=58634> tid=0x50] No longer suspecting 10.32.111.26(locatorp2_host2_12681:12681:locator)<ec><v0>:41000

[info 2019/09/24 10:05:18.756 PDT <P2P message reader for 10.32.111.26(bridgep2_host2_12641:12641)<v2>:41002
shared ordered uid=6 port=58664> tid=0x58] No longer suspecting 10.32.111.26(bridgep2_host2_12641:12641)<v2>:41002

[info 2019/09/24 10:05:22.449 PDT <Geode Failure Detection thread 4> tid=0x6e] Availability
check failed but detected recent message traffic for suspect member 10.32.111.26(bridgep2_host2_12641:12641)<v2>:41002

[info 2019/09/24 10:05:22.450 PDT <Geode Failure Detection thread 4> tid=0x6e] Availability
check passed for suspect member 10.32.111.26(bridgep2_host2_12641:12641)<v2>:41002

[info 2019/09/24 10:05:22.453 PDT <Geode Failure Detection thread 9> tid=0x73] Availability
check failed for member 10.32.111.26(locatorp2_host2_12671:12671:locator)<ec><v1>:41001
{noformat}

> 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 J Schuchardt
>            Assignee: Bruce J 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.4#803005)

Mime
View raw message