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 2020/07/15 04:26:00 UTC

[jira] [Commented] (GEODE-7384) OldId from the same distributed member should be removed when processing the dm's PrepareNewPersistentMemberMessage

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

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

Commit b2087a84ee1c2febefa150f072b6502727c3a64c in geode's branch refs/heads/feature/GEODE-8360 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b2087a8 ]

Revert "GEODE-7384: Members's old Persistent Member Id should be removed (#4257)"

This reverts commit ba21b6345c0e9158549d2958a268d1fc0b7f38f7.


> OldId from the same distributed member should be removed when processing the dm's PrepareNewPersistentMemberMessage
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7384
>                 URL: https://issues.apache.org/jira/browse/GEODE-7384
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence
>    Affects Versions: 1.1.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: GeodeCommons
>             Fix For: 1.11.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The old id is being removed only if the PersistenceAdvisorImpl is initialized when processing the message. However, this could lead to two PersistentMemberIDs from the same member being persisted and there is no way that the old id can be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)