[
https://issues.apache.org/jira/browse/GEODE-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787158#comment-16787158
]
ASF subversion and git services commented on GEODE-6477:
--------------------------------------------------------
Commit 81ca45754bb5c303d305c3fe8fb04a4d4f4e12bd in geode's branch
refs/heads/develop from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=81ca457 ]
Revert "GEODE-6477: Reply with exception if exception occurred during
processing the message. (#3258)"
Do not change the existing product behavior as other places send the message as
well.
Instead I will open a new ticket to handle the issue seen during gii.
This reverts commit a441757759819afa1fcfc3a36e10d4f22e762abe.
> 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
> Fix For: 1.10.0
>
> 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)
