[
https://issues.apache.org/jira/browse/GEODE-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847145#comment-16847145
]
ASF subversion and git services commented on GEODE-6802:
--------------------------------------------------------
Commit da960f389d5c54a23f6bfa33363b637b550bafb4 in geode's branch
refs/heads/feature/GEODE-6802 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=da960f3 ]
GEODE-6802: Execute region synchronization on newly joined member.
* Region sync will be invoked to avoid data inconsistency on a newly
joined/restarted member
if it received a region synchronization request from other members due to
timed task.
* Use a flag in RegionVersionHolder to ensure only one such call is executed.
* Make sure RVV exception is filled for persistent member requesting region
sync. (This may
leads to CommitConflictException on some transactions on persistent regions
due to this
region sync operation. But it should be rare and is acceptable compared to
data inconsistency
issue.)
> 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
>
> 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
(v7.6.3#76005)
