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 2019/03/04 17:26:01 UTC

[jira] [Commented] (GEODE-6477) GII provider should indicate that it does not persist the requester's new persistent id when processing PrepareNewPersistentMemberMessage during shutdown

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

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

Commit a441757759819afa1fcfc3a36e10d4f22e762abe in geode's branch refs/heads/develop from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a441757 ]

GEODE-6477: Reply with exception if exception occurred during processing the message. (#3258)



> GII provider should indicate that it does not persist the requester's new persistent id when processing PrepareNewPersistentMemberMessage during shutdown
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6477
>                 URL: https://issues.apache.org/jira/browse/GEODE-6477
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, provide does not persist the requester's new persistent id during shutdown but it does not send a message to indicate this. The requester could then request gii from the provider and then persists its new persistent id and assume the provider has persisted its new id. And then it is being shut down as well.
> The end result is a requester could not be restarted if provider was recovered first (shut down all case), as provider does not know the requester's new persistent id and ConflictingPersistentDataException is raised.



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