[
https://issues.apache.org/jira/browse/IGNITE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107779#comment-18107779
]
Ignite TC Bot commented on IGNITE-28612:
----------------------------------------
{panel:title=Branch: [pull/13515/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13515/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 12{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9305629]]
* {color:#013220}IgniteCacheTestSuite12:
TxSavepointNearCacheVisibilityTest.testRolledBackEntryVisibleWithoutRemoteUnlock
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9305766&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9305766
rerunBuildIds=9306693,9306695{color}
> 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
> Attachments: TxSavepointNearCacheVisibilityTest.java
>
> 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)
