[
https://issues.apache.org/jira/browse/GEODE-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivanac resolved GEODE-5557.
---------------------------------
Resolution: Fixed
> enabling read conflict detection may cause transactions to fail with a
> conflict on entries that are never written
> -----------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-5557
> URL: https://issues.apache.org/jira/browse/GEODE-5557
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Affects Versions: 1.0.0-incubating
> Reporter: Darrel Schneider
> Assignee: Mario Ivanac
> Priority: Major
> Labels: SmallFeature, needs-review, pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> Read conflict detection can be enabled with
> -Dgemfire.detectReadConflicts=true.
> If this is done then a transaction can fail because it read an entry that
> some one else modified.
> But it is possible that this feature will cause your transaction to fail
> because some other transaction read an entry that you read or wrote. These
> are not valid conflicts.
> This bug is caused by the way TXReservationMgr checks for conflicts. It
> treats every key sent to it as if it was written and when read confliction
> detection is enabled keys we only read are sent to it.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
