[
https://issues.apache.org/jira/browse/HDFS-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5076:
----------------------------
Description: 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). (was: 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 servlets to enable querying these
information through http, so that administrators and applications like Ambari
can easily decide if a forced checkpoint by calling saveNamespace is necessary.)
> 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
