[
https://issues.apache.org/jira/browse/IGNITE-29173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134037#comment-18134037
]
Ignite TC Bot commented on IGNITE-29173:
----------------------------------------
{panel:title=Branch: [pull/13765/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13765/head] Base: [master] : New Tests
(25)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Control Utility 1{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=9450595]]
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testKillLock[cmdHnd=jmx] - PASSED{color}
* {color:#013220}IgniteControlUtilityTestSuite:
KillCommandsControlShTest.testKillLock[cmdHnd=cli] - PASSED{color}
{color:#00008b}Cache 16{color} [[tests
23|https://ci2.ignite.apache.org/viewLog.html?buildId=9450688]]
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillPendingLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testServiceLeftLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testJobLeftLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testInterruptedJobLeftLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillUnknownLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillAcquiredLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testLocalInternalJobKeepsLock[near=false] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillPartiallyAcquiredLock[near=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testInterruptedJobLeftLock[near=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillUnknownLock[near=true] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite14:
ExplicitLockKillTest.testKillAcquiredLock[near=true] - PASSED{color}
... and 12 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9450702&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9450702
rerunBuildIds=none{color}
> Kill lock command
> -----------------
>
> Key: IGNITE-29173
> URL: https://issues.apache.org/jira/browse/IGNITE-29173
> Project: Ignite
> Issue Type: New Feature
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In some scenarios explicit cache locks can leak. For example, an application
> may call cache.lock(key).lock() without a matching lock.unlock() (a missing
> or skipped
> unlock() in user code, an exception thrown between acquiring the lock and
> releasing it, etc.). In such a case the lock is never released.
> There is currently no way to remove such a lock:
> - the lock is not bound to a transaction, so neither KILL TRANSACTION
> nor TransactionMXBean can help;
> - existing KILL subcommands (scan, sql, continuous, all, ...) do not
> cover explicit cache locks.
> Add a new management command to the control utility that allows an
> administrator to forcibly cancel an explicit cache lock identified by its
> lock ID (XID):
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
