[
https://issues.apache.org/jira/browse/HADOOP-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-3121:
-------------------------------------------
Fix Version/s: 0.18.3
> Shouldn't it be the same for other exceptions? What if dir '/a' does not have
> permissions for this user?
Since this issue is target for 0.18, I don't want to introduce big changes.
How about we fix other exceptions in a separated issue?
> 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
> Fix For: 0.18.3
>
> 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.
