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 "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2008/11/05 01:54:44 UTC

[jira] Updated: (HADOOP-3121) dfs -lsr fail with "Could not get listing "

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

Tsz Wo (Nicholas), SZE updated HADOOP-3121:
-------------------------------------------

    Assignee: Tsz Wo (Nicholas), SZE

This seems already fixed in trunk.  At least, the behavior should be different since I could not find "Could not get listing " in the ls codes.  I will check this in details.

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