[ https://issues.apache.org/jira/browse/HDFS-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740297#comment-13740297 ]
Hadoop QA commented on HDFS-5076: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12598048/HDFS-5076.004.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4822//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4822//console This message is automatically generated. > Add MXBean methods to query NN's transaction information and JournalNode's > journal status > ----------------------------------------------------------------------------------------- > > Key: HDFS-5076 > URL: https://issues.apache.org/jira/browse/HDFS-5076 > Project: Hadoop HDFS > Issue Type: New Feature > Affects Versions: 3.0.0 > Reporter: Jing Zhao > Assignee: Jing Zhao > Priority: Minor > Attachments: HDFS-5076.001.patch, HDFS-5076.002.patch, > HDFS-5076.003.patch, HDFS-5076.004.patch > > > Currently NameNode already provides RPC calls to get its last applied > transaction ID and most recent checkpoint's transaction ID. It can be helpful > to provide support to enable querying these information through JMX, so that > administrators and applications like Ambari can easily decide if a forced > checkpoint by calling saveNamespace is necessary. Similarly we can add MxBean > interface for JournalNodes to query the status of journals (e.g., whether > journals are formatted or not). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira