Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <3571616.433811285632934918.JavaMail.jira@thor>
Date: Mon, 27 Sep 2010 20:15:34 -0400 (EDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Moved: (MAPREDUCE-2093) CLONE -Herriot NN and DN clients
 should vend statistics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Boudnik moved HDFS-1424 to MAPREDUCE-2093:
-----------------------------------------------------

              Project: Hadoop Map/Reduce  (was: Hadoop HDFS)
                  Key: MAPREDUCE-2093  (was: HDFS-1424)
    Affects Version/s: 0.22.0
                           (was: 0.22.0)
          Component/s: test
                           (was: test)

> CLONE -Herriot NN and DN clients should vend statistics
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-2093
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2093
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>
> The HDFS web user interface serves useful information through dfshealth.jsp and dfsnodelist.jsp.
> The Herriot interface to the namenode and datanode (as implemented in NNClient and DNClient, respectively) would benefit from the addition of some way to channel this information. In the case of DNClient this can be an injected method that returns a DatanodeDescriptor relevant to the underlying datanode.
> There seems to be no analagous NamenodeDescriptor. It may be useful to add this as a facade to a visitor that aggregates values across the filesystem datanodes. These values are (from dfshealth JSP):
> Configured Capacity
> DFS Used
> Non DFS Used
> DFS Remaining
> DFS Used%
> DFS Remaining%
> Live Nodes
> Dead Nodes
> Decommissioning Nodes
> Number of Under-Replicated Blocks
> Attributes reflecting the web user interface header may also be useful such as When-Started, Version, When-Compiled, and Upgrade-Status.
> A NamenodeDescriptor would essentially "push down" the code in dfshealth web UI behind a more general abstraction. If it is objectionable to make this class available in HDFS, perhaps this could be packaged in a Herriot specific way.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.