[
https://issues.apache.org/jira/browse/HDFS-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-5076:
----------------------------
Attachment: HDFS-5076.004.patch
Update the patch to address Suresh's comments: add a new method which takes
journal id as parameter and returns its status.
bq. In journal status should we also return the address and port of the Journal
node?
Currently we put the MXBean to each JournalNode. Thus when querying the jmx the
user should already have the knowledge about the corresponding JournalNode. So
I think maybe here we do not need to return the address and port of the JN.
> Create http servlets to enable querying NN's last applied transaction ID and
> most recent checkpoint's transaction ID
> --------------------------------------------------------------------------------------------------------------------
>
> 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 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.
--
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
