[ 
https://issues.apache.org/jira/browse/GEODE-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526239#comment-17526239
 ] 

ASF subversion and git services commented on GEODE-10229:
---------------------------------------------------------

Commit d6d96d465a62d009836552a1d0dabadb1637c9c4 in geode's branch 
refs/heads/support/1.14 from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d96d465a ]

GEODE-10229: GII image should fill disk region RVV's exceptions. (#7602)

* GEODE-10229: GII image should fill disk region RVV's exceptions.
    There're 2 issues: Tombstone in GII image should save version tag into disk 
region RVV
    even the tombstone is the same as local one. Disk region RVV holder did not 
use bitset.
    Only bitset based holder can fill special exception. Should do it for 
non-bitset holder too.

(cherry picked from commit 28dbac1a86dd40ca0c3ceba004263824f6de4653)


> Saving received RVV's caused exception should be filled.
> --------------------------------------------------------
>
>                 Key: GEODE-10229
>                 URL: https://issues.apache.org/jira/browse/GEODE-10229
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Xiaojian Zhou
>            Assignee: Xiaojian Zhou
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>             Fix For: 1.15.0
>
>
> Saving received RVV's caused exception should be filled during processing GII 
> image
> There's a race in GII: 
> A distribution of operation (RemoveAll could be more obvious) arrived when 
> the member is requesting GII and before saving received RVV. The 
> saveReceivedRVV() will the newly arrived operation to be an exception. 
> In normal case, the exception will be filled in processChunk(). But in above 
> case, the processChunk() will skip the entry because the local entry is not 
> recovered from disk. 
> Thus the exception will stay after GII. 
> To fix it, and not to slow down the performance, we need to check if such 
> exception exists, and do the recordVersion() for this entry. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to