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

Hudson commented on HDDS-707:
-----------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #15280 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15280/])
HDDS-707. Allow registering MBeans without additional jmx properties. 
(aengineer: rev c9077a9f5a693df63c2ff797415605233e38a9a8)
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/RocksDBStore.java
* (edit) 
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/StorageContainerManager.java
* (edit) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/HddsUtils.java
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/db/RDBStore.java
* (edit) 
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java


> Allow registering MBeans without additional jmx properties
> ----------------------------------------------------------
>
>                 Key: HDDS-707
>                 URL: https://issues.apache.org/jira/browse/HDDS-707
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: OM, Ozone Datanode, SCM
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>            Priority: Blocker
>         Attachments: HDDS-707.01.patch, HDDS-707.02.patch, HDDS-707.03.patch
>
>
> HDDS and Ozone use the MBeans.register overload added by HADOOP-15339. This 
> is missing in Apache Hadoop 3.1.0 and earlier. This prevents us from building 
> Ozone with earlier versions of Hadoop. More commonly, we see runtime 
> exceptions if an earlier version of the Hadoop-common jar happens to be in 
> the classpath.
> Let's add a reflection-based switch to invoke the right version of the API so 
> we can build and use Ozone with Apache Hadoop 3.1.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to