You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/19 16:08:00 UTC

[jira] [Commented] (GEODE-5402) Disk recovery sometimes hangs when no member is recognized as having the most recent data

    [ https://issues.apache.org/jira/browse/GEODE-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549466#comment-16549466 ] 

ASF subversion and git services commented on GEODE-5402:
--------------------------------------------------------

Commit 3366f51356f0b7900f5fcb17afe84760959fbe73 in geode's branch refs/heads/develop from lgallinat
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3366f51 ]

GEODE_5402 Disk recovery hangs after killing members (#2148)

GEODE-5402 Fix issue where disk recovery hangs when all members are waiting for other members to proceed.


> Disk recovery sometimes hangs when no member is recognized as having the most recent data 
> ------------------------------------------------------------------------------------------
>
>                 Key: GEODE-5402
>                 URL: https://issues.apache.org/jira/browse/GEODE-5402
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Lynn Gallinat
>            Assignee: Lynn Gallinat
>            Priority: Major
>
> During disk recovery, sometimes a the system will hang because every member is waiting for others to initialize first, and nobody is recognized as having the most recent data.
> This can happen when a member persists its most recent view of another member to disk, then that member is killed before it can remove the older view of the other member from the op log files. When starting the cluster from disk, the member then has two views of the other member, one recent and the other stale. The member then decides is needs to wait for the stale view of the other member which causes the hang.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)