[
https://issues.apache.org/jira/browse/IGNITE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107823#comment-18107823
]
Kirill Tkalenko commented on IGNITE-28612:
------------------------------------------
Looks good.
> 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
> Fix For: 2.19
>
> Attachments: TxSavepointNearCacheVisibilityTest.java
>
> Time Spent: 20m
> 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)