[
https://issues.apache.org/jira/browse/GEODE-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick Cavender closed GEODE-6802.
--------------------------------
> Data/bucket (among redundant copies) inconsistence could occur after a member
> is lost
> -------------------------------------------------------------------------------------
>
> Key: GEODE-6802
> URL: https://issues.apache.org/jira/browse/GEODE-6802
> Project: Geode
> Issue Type: Bug
> Components: persistence, regions
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> When a prime bucket(or replicate region) is lost during the operation, it
> could occur at a time it only sent the operation to only part of the
> replicates (redundant copies), but not to others. Geode does region
> synchronization after some delay using a timed task to sync with all other
> members.
> When the lost member restarted (or new nodes joined), it could request GII
> from a source (before region sync occurred) did not receive the original
> operation. This restarted member or new member does not have the timed task
> which triggered by the original member departed event. This could lead to
> data inconsistence among the members.
> In addition, for persistent members, there could be some exception occurred
> during GII, and region synchronization provider would not send necessary data
> to the requester and thus lead to data inconsistency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
