[
https://issues.apache.org/jira/browse/GEODE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686932#comment-16686932
]
ASF subversion and git services commented on GEODE-6013:
--------------------------------------------------------
Commit 09dd194f5a423ea591c0f47d3114df46d23435e8 in geode's branch
refs/heads/develop from Anil
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=09dd194 ]
Revert "GEODE-6013: Made changes to use the expected initial image requester's
rvv information (#2819)"
This reverts commit b4befb99626e85045379e5b6fb8804b9db2a3eb9.
> A recovered node may not be consistent with peer after getting initial image
> ----------------------------------------------------------------------------
>
> Key: GEODE-6013
> URL: https://issues.apache.org/jira/browse/GEODE-6013
> Project: Geode
> Issue Type: Bug
> Components: regions
> Affects Versions: 1.7.0
> Reporter: Anilkumar Gingade
> Assignee: Anilkumar Gingade
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> A node recovered from its persistent data may not receive all the expected
> data from peer after doing GII (delta); if there is an ongoing tombstone GC
> at the GII (get initial image) provider; resulting data inconsistency between
> the replicas.
> While doing code walk through noticed that; when a node comes up with the
> persistent data requests delta GII from another replica (GII provider); at
> the provider side while comparing the tombstone GC version to determine
> whether to perform full or Delta GII, the provider was using its GC version
> instead of requester's gc version, resulting in performing delta GII instead
> of full gii.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
