You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/08/07 22:55:50 UTC
[jira] [Updated] (HDFS-5076) Create http servlets to enable
querying NN's last applied transaction ID and most recent checkpoint's
transaction ID
[ 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.001.patch
Initial patch for review. Besides the two tx ids mentioned in the description, the patch also adds a servlet on Journal Node to allow users to learn if the JN has been successfully formatted. We can also move this to a separate jira if necessary.
> 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
>
>
> 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