You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (JIRA)" <ji...@apache.org> on 2019/04/24 22:23:24 UTC

[jira] [Closed] (GEODE-6013) A recovered node may not be consistent with peer after getting initial image

     [ https://issues.apache.org/jira/browse/GEODE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen Nichols closed GEODE-6013.
-------------------------------

> 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 40m
>  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)