[
https://issues.apache.org/jira/browse/HADOOP-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton reopened HADOOP-15339:
-----------------------------------
Since the commit we use this change from ozone/hdds and it worked well.
This change is required to have a working ozone/hdds webui as the shared code
path tags the common jmx beans with generic key/value tags.
I reopen this issue and propose to backport it to branch-3.1 to make it easier
to use hdds/ozone with older hadoop versions.
# It's a small change
# Backward compatible
# Safe to use (no issue during the last 6 months)
# No conflicts for cherry-pick.
> Support additional key/value propereties in JMX bean registration
> -----------------------------------------------------------------
>
> Key: HADOOP-15339
> URL: https://issues.apache.org/jira/browse/HADOOP-15339
> Project: Hadoop Common
> Issue Type: Improvement
> Components: common
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: HADOOP-15339.001.patch, HADOOP-15339.002.patch,
> HADOOP-15339.003.patch
>
>
> org.apache.hadoop.metrics2.util.MBeans.register is a utility function to
> register objects to the JMX registry with a given name prefix and name.
> JMX supports any additional key value pairs which could be part the the
> address of the jmx bean. For example:
> _java.lang:type=MemoryManager,name=CodeCacheManager_
> Using this method we can query a group of mbeans, for example we can add the
> same tag to similar mbeans from namenode and datanode.
> This patch adds a small modification to support custom key value pairs and
> also introduce a new unit test for MBeans utility which was missing until now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
