[
https://issues.apache.org/jira/browse/IGNITE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-28612:
---------------------------------------
Description:
h3. Motivation
During rollbackToSavepoint(), the near lock was released, but the corresponding
near-cache entry containing the old value remained valid. Its eviction depended
on asynchronous remote unlock processing. A concurrent update could therefore
complete on the primary while reads on the transaction initiator still returned
the stale near-cache value.
h3. Definition of done
The attached test ought to pass.
was:
h3. Motivation
It is not a big issue, but nevertheless, a sequential guarantee is not to be
violated even in case the updates come through the different nodes.
I believe this is an issue in a near cache, because if I wait several extra
milliseconds before checking the cache, it passes.
h3. Definition of done
The attached test ought to pass.
> Stale near-cache value may be returned after rollback to savepoint
> ------------------------------------------------------------------
>
> Key: IGNITE-28612
> URL: https://issues.apache.org/jira/browse/IGNITE-28612
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> During rollbackToSavepoint(), the near lock was released, but the
> corresponding near-cache entry containing the old value remained valid. Its
> eviction depended on asynchronous remote unlock processing. A concurrent
> update could therefore complete on the primary while reads on the transaction
> initiator still returned the stale near-cache value.
> h3. Definition of done
> The attached test ought to pass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
