[
https://issues.apache.org/jira/browse/IGNITE-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985861#comment-16985861
]
Vladislav Pyatkov edited comment on IGNITE-12393 at 12/2/19 7:13 AM:
---------------------------------------------------------------------
Hi,
I think, view of queue through system view will not be enough to understanding
what issue that is. But striped pool monitoring is right approach, but need to
do it more human understandable. In general we are already getting all queue's
items in log when starvation detected, but it does not suitable.
I think so only list of message in queue will not be useful for high level user.
I will want to see statistic information:
# What is duration of handle of particular message?
# How long the message hold in the queue?
# What is the message mean? (in human readable format)
# How to determine not typical duration of message?
was (Author: v.pyatkov):
Hi,
I am think view of queue through system view will be not enough to
understanding what issue that is. But striped pool monitoring is right
approach, but need to do it more human understandable. In general we are
already getting all queue's items in log when starvation detected, but it does
not suitable.
I think so only list of message in queue will not be useful for high level user.
I will want to see statistic information:
# What is duration of handle of particular message?
# How long the message hold in the queue?
# What is the message mean? (in human readable format)
# How to determine not typical duration of message?
> 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)
