[ 
https://issues.apache.org/jira/browse/IGNITE-12393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985891#comment-16985891
 ] 

Nikolay Izhikov commented on IGNITE-12393:
------------------------------------------

[~v.pyatkov]

> I think, view of queue through system view will not be enough to understanding

You are right. 
This view is only one view of Ignite's internal processes.
We should take other monitoring features in the count to see the whole picture.

> What is duration of handle of particular message?

It seems it should be the metric that shows the time when the last {{Runnable}} 
was peeked up from stripe.

> How long the message hold in the queue?

Yes, you are right. 
I thought to add this number to the view.
But this will require changes in {{StripedPool}} implementation.
We also can have performance issues with the extra long field for each Runnable 
in the pool.
I think we should add this in the other ticket.

What do you think?

> What is the message mean? (in human readable format)

I don't this we should implement it in {{SystemView}}.
Translation from Ignite specific to human-readable if a feature of a 
third-party tool.

> How to determine not typical duration of message?

This covers by the Failure Handler feature for Ignite internals, isn't it?

> 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)

Reply via email to