You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2008/11/27 01:46:44 UTC

[jira] Updated: (HADOOP-4029) NameNode should report status and performance for each replica of image and log

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

Boris Shkolnik updated HADOOP-4029:
-----------------------------------

    Attachment: HADOOP-4029.patch

This patch include the following changes:
1. additional storage directory (in Storage class) to keep removed(failed) storages and accessors to this list
2. changes to FSImage to add storages to this list (when IO failes)
3. changes to the dfshealth.jsp page to display both lists (valid and failed storages)
4. List of live/dead nodes is moved to a separate page.

> NameNode should report status and performance for each replica of image and log
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-4029
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4029
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.18.0
>            Reporter: Robert Chansler
>            Assignee: Boris Shkolnik
>         Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica. In addition to reporting whether the replica is active or not, measured performance should be reported so as to indicate whether a replica might impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can give the administrator some clues.

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