[
https://issues.apache.org/jira/browse/HDFS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-927:
-----------------------------
Attachment: hdfs-927.txt
The crux of this issue is that the original HDFS-127 patch was bad. I'm not
sure why it caused an infinite loop on 0.20 but not on later branches, but
either way it doesn't do what it was supposed to.
This patch adds test cases to check infinite loop behavior and also to verify
that the correct number of retries are taken. I also took the approach I
outlined at
https://issues.apache.org/jira/browse/HDFS-127?focusedCommentId=12803077&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12803077
to fix HDFS-127's retry logic.
> DFSInputStream retries too many times for new block locations
> -------------------------------------------------------------
>
> Key: HDFS-927
> URL: https://issues.apache.org/jira/browse/HDFS-927
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Attachments: hdfs-927.txt
>
>
> I think this is a regression caused by HDFS-127 -- DFSInputStream is supposed
> to only go back to the NN max.block.acquires times, but in trunk it goes back
> twice as many - the default is 3, but I am counting 7 calls to
> getBlockLocations before an exception is thrown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
