[jira] [Commented] (HDFS-12286) Ozone: Extend MBeans utility to add any key value pairs to the registered MXBeans
[ https://issues.apache.org/jira/browse/HDFS-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450941#comment-16450941 ] Hudson commented on HDFS-12286: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/]) HDFS-12286. Ozone: Extend MBeans utility to add any key value pairs to (aengineer: rev 4fac755bc765291197c3ead2846f4f4fd7332100) * (add) hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/metrics2/util/DummyMXBean.java * (edit) hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/metrics2/util/MBeans.java * (add) hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/metrics2/util/TestMBeans.java > Ozone: Extend MBeans utility to add any key value pairs to the registered > MXBeans > - > > Key: HDFS-12286 > URL: https://issues.apache.org/jira/browse/HDFS-12286 > Project: Hadoop HDFS > Issue Type: Sub-task >Affects Versions: HDFS-7240 >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: HDFS-7240 > > Attachments: HDFS-12286-HDFS-7240.001.patch, jmx1.png, jmx2.png > > > The MBeans class in hadoop-common helps to register MXBean to the platform > jmx bean. Unfortunatelly it supports only Name and Service keys even if the > JMX specification allows any key value pairs to use as a part of the > ObjectName. > This patch adds the possibility to define more key/value pairs for the JMX > ObjectName. > It will be usefull for the SCM/KSM web page. Both SCM/KSM Server have common > jmx properties. But to use a common html component to display them we need a > possibility to get the JMX bean of SCM server and KSM server with one query. > This will be possible with adding additional (common) key/value property to > the ObjectName. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12286) Ozone: Extend MBeans utility to add any key value pairs to the registered MXBeans
[ https://issues.apache.org/jira/browse/HDFS-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123486#comment-16123486 ] Anu Engineer commented on HDFS-12286: - [~elek] Thanks for the screen shots and explanation. +1, I will commit this shortly. > Ozone: Extend MBeans utility to add any key value pairs to the registered > MXBeans > - > > Key: HDFS-12286 > URL: https://issues.apache.org/jira/browse/HDFS-12286 > Project: Hadoop HDFS > Issue Type: Sub-task >Affects Versions: HDFS-7240 >Reporter: Elek, Marton >Assignee: Elek, Marton > Fix For: HDFS-7240 > > Attachments: HDFS-12286-HDFS-7240.001.patch, jmx1.png, jmx2.png > > > The MBeans class in hadoop-common helps to register MXBean to the platform > jmx bean. Unfortunatelly it supports only Name and Service keys even if the > JMX specification allows any key value pairs to use as a part of the > ObjectName. > This patch adds the possibility to define more key/value pairs for the JMX > ObjectName. > It will be usefull for the SCM/KSM web page. Both SCM/KSM Server have common > jmx properties. But to use a common html component to display them we need a > possibility to get the JMX bean of SCM server and KSM server with one query. > This will be possible with adding additional (common) key/value property to > the ObjectName. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12286) Ozone: Extend MBeans utility to add any key value pairs to the registered MXBeans
[ https://issues.apache.org/jira/browse/HDFS-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122013#comment-16122013 ] Anu Engineer commented on HDFS-12286: - [~elek] The patch looks good to me. I have a question before we commit this. Suppose I create a JMX with additional properties. How will it look when I access it via the http://namenode:port/jmx, does the additional properties show up as normal key values in JSON ? > Ozone: Extend MBeans utility to add any key value pairs to the registered > MXBeans > - > > Key: HDFS-12286 > URL: https://issues.apache.org/jira/browse/HDFS-12286 > Project: Hadoop HDFS > Issue Type: Sub-task >Affects Versions: HDFS-7240 >Reporter: Elek, Marton >Assignee: Elek, Marton > Fix For: HDFS-7240 > > Attachments: HDFS-12286-HDFS-7240.001.patch > > > The MBeans class in hadoop-common helps to register MXBean to the platform > jmx bean. Unfortunatelly it supports only Name and Service keys even if the > JMX specification allows any key value pairs to use as a part of the > ObjectName. > This patch adds the possibility to define more key/value pairs for the JMX > ObjectName. > It will be usefull for the SCM/KSM web page. Both SCM/KSM Server have common > jmx properties. But to use a common html component to display them we need a > possibility to get the JMX bean of SCM server and KSM server with one query. > This will be possible with adding additional (common) key/value property to > the ObjectName. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
