[ https://issues.apache.org/jira/browse/GEODE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anilkumar Gingade reopened GEODE-6013: -------------------------------------- There could be possibility of NPE with the change made, at: in org.apache.geode.internal.cache.versions.RegionVersionVector.isGCVersionDominatedByOtherHolder(RegionVersionVector.java:986) in org.apache.geode.internal.cache.versions.RegionVersionVector.isRVVGCDominatedBy(RegionVersionVector.java:1023) > 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)