[ 
https://issues.apache.org/jira/browse/IGNITE-13044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stanilovsky Evgeny updated IGNITE-13044:
----------------------------------------
    Summary: Additional possibility to check for high contending keys generated 
by the transaction payload.  (was: Additional possibility to check for high 
contending keys through transactional payload.)

> Additional possibility to check for high contending keys generated by the 
> transaction payload.
> ----------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13044
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13044
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.8
>            Reporter: Stanilovsky Evgeny
>            Assignee: Stanilovsky Evgeny
>            Priority: Major
>
> In process of limited keys highload updates there are possible to obtain high 
> queue of locking candidates. Want to be able for monitoring such situations, 
> jmx seems to be correct place for it. Any additional info would be append 
> here after pr approval and resolution also appropriate documentation ticket, 
> of course, need to be linked.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to