hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6203) Improve error message when moving to trash fails due to quota issue
Date Tue, 01 Sep 2009 17:12:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749996#action_12749996

Suresh Srinivas commented on HADOOP-6203:

I prefer the shorter message from the existing patch as output instead of printing the exception
message in the output. Given that the layer where error is being printed does not have specific
nature of error, such as, quota exceeded this seems like the best thing to do.

Looking at the output which says {{rm: Failed to move to trash: hdfs://localhost:9000/file3
}}, the existing output (prior to the patch) already indicates a trash related error. The
value add of this patch is that the output indicates the user can work around the problem
by using the -skipTrash option.

I am +1 for the change if Koji agrees that the existing output captures sufficient information
for the user.

> Improve error message when moving to trash fails due to quota issue
> -------------------------------------------------------------------
>                 Key: HADOOP-6203
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6203
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Jakob Homan
>            Assignee: Boris Shkolnik
>         Attachments: HADOOP-6203.patch, HADOOP-6203.patch
> HADOOP-6080 provided an option for deleting files even when overquota, but the error
message that's returned in this situation is unhelpful and doesn't suggest skipTrash as a
> {noformat}$ hdfs -rmr /foo/bar/bat/boo
> rmr: Failed to move to trash:
> hdfs://cluster/foo/bar/bat/boo{noformat}
> In this situation, the error message should say there was a quote problem and suggest

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

View raw message