[
https://issues.apache.org/jira/browse/GEODE-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-8672:
----------------------------------
Labels: pull-request-available (was: )
> 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
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
> Labels: pull-request-available
>
> 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)
