[jira] [Updated] (IGNITE-9921) Local Node Job Metrics are not displayed
[ 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)
[jira] [Updated] (IGNITE-9921) Local Node Job Metrics are not displayed
[ https://issues.apache.org/jira/browse/IGNITE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kapralov updated IGNITE-9921: -- Security: (was: Private) > 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 > > 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. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511486#comment-16511486 ] Ivan Kapralov edited comment on IGNITE-8402 at 6/13/18 6:19 PM: Facing necessity to monitor long running transactions parameters on cluster nodes via JMX. Solution implemented in IGN-7910 is unfortunately inappropriate, because can not be run by automatic monitoring systems. was (Author: ivan kapralov): Facing necessity to monitor long running transactions parameters on cluster nodes via JMX. > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > Fix For: 2.5 > > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kapralov reopened IGNITE-8402: --- Facing necessity to monitor long running transactions parameters on cluster nodes via JMX. > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > Fix For: 2.5 > > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kapralov resolved IGNITE-8402. --- Resolution: Implemented Fix Version/s: (was: None) 2.5 Implemented in https://issues.apache.org/jira/browse/IGNITE-7910 > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > Fix For: 2.5 > > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kapralov updated IGNITE-8402: -- Description: Facing necessity in Long Running Transactions JMX metric implementation. Needed: transaction start time, node ID, duration, cache full qualified name, originator ID. was: Facing necessity in Long Running Transactions JMX metric implementation. Needed: transaction start time, node ID, duration, cache ID, originator ID comma separated in the same string. Info about transactions that are hung up for more than 600 sec. > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > Fix For: None > > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8402) Long running transaction JMX
Ivan Kapralov created IGNITE-8402: - Summary: Long running transaction JMX Key: IGNITE-8402 URL: https://issues.apache.org/jira/browse/IGNITE-8402 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.4 Reporter: Ivan Kapralov Fix For: None Facing necessity in Long Running Transactions JMX metric implementation. Needed: transaction start time, node ID, duration, cache ID, originator ID comma separated in the same string. Info about transactions that are hung up for more than 600 sec. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
