Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 8 Aug 2013 20:14:47 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12662475.1375906050151.27463.1375992887829@arcas>
In-Reply-To: <JIRA.12662475.1375906050151@arcas>
References: <JIRA.12662475.1375906050151@arcas>
Subject: [jira] [Updated] (HDFS-5076) Create http servlets to enable
 querying NN's last applied transaction ID and most recent checkpoint's
 transaction ID
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Zhao updated HDFS-5076:
----------------------------

    Status: Patch Available  (was: Open)
    
> 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