[
https://issues.apache.org/jira/browse/GEODE-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226391#comment-17226391
]
ASF subversion and git services commented on GEODE-8672:
--------------------------------------------------------
Commit 7367d17e3817fc41666d471c5eb4d0df0d33c18b in geode's branch
refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7367d17 ]
Revert "GEODE-8672: No need in token mode if concurrencyChecksEnabled (#5691)"
(#5702)
This reverts commit e695938dff4b39f1755c707e81e1eb7e2e143fe0.
> Concurrent transactional destroy with GII could cause an entry to be removed
> and version information to be lost
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-8672
> URL: https://issues.apache.org/jira/browse/GEODE-8672
> Project: Geode
> Issue Type: Bug
> Components: regions
> Affects Versions: 1.1.0
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In a newly rebalanced bucket, while GII is in progress, a transactional
> destroy is applied to cache. There is a logic that it should be in token mode
> and leaves the entry as a Destroyed token, even though the version tag of the
> entry indicates that it has the correct version.
> However, at end of the GII, there is a
> cleanUpDestroyedTokensAndMarkGIIComplete method removes all the destroyed
> entries – this wipes off the entry version tag information and cause the
> subsequent creates starts fresh with new version tags.
> This could leads to client server data inconsistency as the newly created
> entries will be ignored by the clients as the newly created entry has lower
> version number while client has high ones.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
