You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/06/10 14:51:00 UTC
[jira] [Commented] (IGNITE-28758) Explicit lock local-DHT callback can race with timeout/cancel cleanup.

    [ https://issues.apache.org/jira/browse/IGNITE-28758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088011#comment-18088011 ] 

Ignite TC Bot commented on IGNITE-28758:
----------------------------------------

{panel:title=Branch: [pull/13227/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13227/head] Base: [master] : New Tests (8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 6{color} [[tests 8|https://ci2.ignite.apache.org/viewLog.html?buildId=9117629]]
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testTryLock[cacheMode=REPLICATED, backups=1] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testCancelRequestOnTimeout[cacheMode=REPLICATED, backups=0] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testTryLock[cacheMode=REPLICATED, backups=0] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testCancelRequestOnTimeout[cacheMode=PARTITIONED, backups=1] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testTryLock[cacheMode=PARTITIONED, backups=1] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testCancelRequestOnTimeout[cacheMode=PARTITIONED, backups=0] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testTryLock[cacheMode=PARTITIONED, backups=0] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6: CacheTryLockMultithreadedTest.testCancelRequestOnTimeout[cacheMode=REPLICATED, backups=1] - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9117742&amp;buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9117742 rerunBuildIds=none{color}

> Explicit lock local-DHT callback can race with timeout/cancel cleanup.
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-28758
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28758
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Major
>              Labels: ise
>             Fix For: 2.19
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> For non-transactional explicit locks, the local DHT lock callback may complete after the outer GridDhtColocatedLockFuture has already been finished by timeout/cancel/error cleanup. In that case cleanup removes the explicit lock candidate, but the late local callback still proceeds to markExplicitOwner(), which can hit GridCacheExplicitLockSpan.markOwned() assertion or leave a locally acquired lock behind.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)