[
https://issues.apache.org/jira/browse/HADOOP-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-3778:
---------------------------------
Affects Version/s: (was: 0.17.1)
0.16.0
Fix Version/s: 0.18.0
This bug existed in hadoop for a long time. Marking it for 0.18. How do assign
it to LN?
> seek(long) in DFSInputStream should catch socket exception for retry later
> --------------------------------------------------------------------------
>
> Key: HADOOP-3778
> URL: https://issues.apache.org/jira/browse/HADOOP-3778
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: LN
> Priority: Minor
> Fix For: 0.18.0
>
> Attachments: HADOOP-3778.patch, HADOOP-3778.patch
>
>
> HADOOP-2346 introduced data read/write timeout. when data stream borken,
> DFSClient will retry in read/write methods, but no such mechanism found when
> seek(long) calling blockReader.skip(diff) (DFSClient.java #1582), will let
> IOException throw to application. i met NPE when using MapFile in hbase.
> i'm supposing in the seek(long) method, let done be 'false' will causing
> retry (via 'blockEnd = -1'), a patch will attached later for review.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
