[
https://issues.apache.org/jira/browse/IGNITE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kapralov updated IGNITE-9921:
----------------------------------
Labels: 2.5.1-next (was: )
Fix Version/s: 2.8
Description:
Metrics CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
CurrentJobWaitTime, CurrentWaitingJobs in bean ClusterLocalNodeMXBeanImpl are
not calculated properly in the following scenario:
- start a server node;
- start a client node that will perform some compute/SQL/put-get tasks;
- CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
CurrentJobWaitTime, CurrentWaitingJobs will always be 0 on both server and
client nodes.
was:
CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
CurrentJobWaitTime, CurrentWaitingJobs are not calculated properly in the
following scenario:
- start a server node;
- start a client node that will perform some compute/SQL/put-get tasks;
- CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
CurrentJobWaitTime, CurrentWaitingJobs will always be 0 on both server and
client nodes.
> Local Node Job Metrics are not displayed
> ----------------------------------------
>
> Key: IGNITE-9921
> URL: https://issues.apache.org/jira/browse/IGNITE-9921
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5, 2.6
> Reporter: Ivan Kapralov
> Priority: Major
> Labels: 2.5.1-next
> Fix For: 2.8
>
>
> Metrics CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
> CurrentJobWaitTime, CurrentWaitingJobs in bean ClusterLocalNodeMXBeanImpl are
> not calculated properly in the following scenario:
> - start a server node;
> - start a client node that will perform some compute/SQL/put-get tasks;
> - CurrentActiveJobs, CurrentCancelledJobs, CurrentJobExecuteTime,
> CurrentJobWaitTime, CurrentWaitingJobs will always be 0 on both server and
> client nodes.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
