Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <356463490.1225925204261.JavaMail.jira@brutus>
Date: Wed, 5 Nov 2008 14:46:44 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3121) dfs -lsr fail with "Could not get
 listing "
In-Reply-To: <267701341.1206730584453.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-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645350#action_12645350 ] 

Raghu Angadi commented on HADOOP-3121:
--------------------------------------


Shouldn't it be the same for other exceptions? What if dir '/a' does not have permissions for this user?


> dfs -lsr fail with "Could not get listing "
> -------------------------------------------
>
>                 Key: HADOOP-3121
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3121
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.16.1
>            Reporter: Koji Noguchi
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Minor
>         Attachments: 3121_20081105.patch
>
>
> (This happened a lot when namenode was extremely slow due to some other reasons.)
> % hadoop dfs -lsr /   
> failed with 
> > Could not get listing for /aaa/bbb/randomfile
> It's probably because  file  was deleted between  items = fs.listStatus( and ls(items[i] 
> I think lsr should ignore this case and continue.

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