hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6986) SequenceFile.Reader should distinguish between Network IOE and Parsing IOE
Date Wed, 28 Dec 2011 21:45:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176828#comment-13176828
] 

Harsh J commented on HADOOP-6986:
---------------------------------

Sorry to come in very late here, but could you rebase the patch onto the 0.23/trunk branches?


I think this is a good change, and +1 to the idea. I trust you've also covered all spots where
we can tweak to also add in parse exceptions.
                
> SequenceFile.Reader should distinguish between Network IOE and Parsing IOE
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-6986
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6986
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 0.20-append, 0.21.1, 0.22.0
>            Reporter: Nicolas Spiegelberg
>            Priority: Minor
>         Attachments: HADOOP-6986_0.21.patch, HADOOP-6986_20-append.patch
>
>
> The SequenceFile.Reader api should give the user an easy way to distinguish between a
Network/Low-level IOE and a Parsing IOE.  The use case appeared recently in the HBase project:
> Originally, if a RegionServer got an IOE from HDFS while opening a region file, it would
abort the open and let the HMaster reassign the region.  The assumption being that this is
a network failure that will likely disappear at a later time or different partition of the
network.  However, if HBase gets parsing exceptions, we want to log the problem and continue
opening the region anyways, because parsing is an idempotent problem and retries won't fix
this issue.
> Although this problem was found in HBase, it seems to be a generic problem of being able
to more easily identify idempotent vs transient errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message