[
https://issues.apache.org/jira/browse/IGNITE-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985578#comment-16985578
]
Stanilovsky Evgeny commented on IGNITE-12393:
---------------------------------------------
[~nizhikov] i think this idea need another realization.
Look, stripe pool objects have (normally) low time to live (fast tx operations
for example) ok i understand that you want to find possible starvation task but
how this view realization will help you - really don`t know. Single thread dump
of starvation job - good approach, but this is not enough of course, you
possible need tx lock, aquire, commit phases log, who takes long lock, long
queries. I know that some prototype was written by [~ascherbakov] ma be hi
gives good advice here too.
> Striped thread pool queue system view
> -------------------------------------
>
> Key: IGNITE-12393
> URL: https://issues.apache.org/jira/browse/IGNITE-12393
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When in the production environment exist some cluster performance issues
> usually it leads to the large striped executor queue size.
> The number of tasks in the queue can observe by
> {StripedExecutorMXBean#getTotalQueueSize} metric. In the case queue size
> becomes large it's useful to have the ability to know what tasks are waiting
> for execution in the thread pool.
> Especially, for dealing with failover scenarios.
> We should create a system views to expose information about striped executor
> services queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
