[
https://issues.apache.org/jira/browse/IGNITE-29277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18143056#comment-18143056
]
Ignite TC Bot commented on IGNITE-29277:
----------------------------------------
{panel:title=Branch: [pull/13816/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13816/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 8{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9488890]]
* {color:#013220}IgniteCacheTestSuite8:
TransactionMetricsTest.testCurrentExplicitLockHoldTime - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9489021&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9489021
rerunBuildIds=none{color}
> Add a histogram of currently held explicit locks
> ------------------------------------------------
>
> Key: IGNITE-29277
> URL: https://issues.apache.org/jira/browse/IGNITE-29277
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Major
> Fix For: 2.20
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{MaxExplicitLockHoldTime}} reports only the longest hold time among the
> explicit locks currently held, and {{ExplicitLockHoldTimeHistogram}} accounts
> for a lock only after it is released, which its name does not say. So there
> is no way to see how many locks are being held for too long right now: a
> single forgotten lock cannot be told apart from a mass leak, and an alert
> cannot be set on the number of such locks. A histogram of hold times of the
> currently held locks is needed, with the two histograms named as a pair,
> {{CurrentExplicitLockHoldTime}} and {{{}ReleasedExplicitLockHoldTime{}}},
> before the existing one is first released.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
