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 "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/10/22 00:04:44 UTC
[jira] Updated: (HADOOP-3778) seek(long) in DFSInputStream should
catch socket exception for retry later
[ https://issues.apache.org/jira/browse/HADOOP-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3778:
------------------------------------
Release Note: (was: DFSInputStream.seek() retries in case of errors just like read().)
> 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: Luo Ning
> Assignee: Luo Ning
> Priority: Minor
> Fix For: 0.19.0
>
> Attachments: HADOOP-3778.patch, 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.