Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <79472318.1251397439279.JavaMail.jira@brutus>
Date: Thu, 27 Aug 2009 11:23:59 -0700 (PDT)
From: "Boris Shkolnik (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-556) Provide info on failed volumes in the
 web ui
In-Reply-To: <1117774212.1250792355153.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748490#action_12748490 ] 

Boris Shkolnik commented on HDFS-556:
-------------------------------------

Well, there are few ways of solving this.
1. print out the "cause" exception together with the error message. That will tell the person that the problem was with Quota. We cannot make suggestions about "-skipTrash" in this case.
2. catch and rethrow exception in delete function when trying to move to Trash. This way we know that the problem is with trash and we can issue a message suggesting using "-skipTrash". The disadvantage is that this way we issue two separate messages.


> Provide info on failed volumes in the web ui
> --------------------------------------------
>
>                 Key: HDFS-556
>                 URL: https://issues.apache.org/jira/browse/HDFS-556
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Jakob Homan
>            Assignee: Boris Shkolnik
>
> HDFS-457 provided better handling of failed volumes but did not provide a corresponding view of this functionality on the web ui, such as a view of which datanodes have failed volumes.  This would be a good feature to have.

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