Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1017193190.1227743564288.JavaMail.jira@brutus>
Date: Wed, 26 Nov 2008 15:52:44 -0800 (PST)
From: "Boris Shkolnik (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Assigned: (HADOOP-4029) NameNode should report status and
 performance for each replica of image and log
In-Reply-To: <169818437.1219787926197.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Boris Shkolnik reassigned HADOOP-4029:
--------------------------------------

    Assignee: Boris Shkolnik

> 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
>
> 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.