hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3506) Occasional NPE in Jets3tFileSystemStore
Date Tue, 26 Aug 2008 01:53:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Douglas updated HADOOP-3506:

       Resolution: Fixed
    Fix Version/s: 0.19.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

+1 Looks good

I just committed this. Thanks, Tom

> Occasional NPE in Jets3tFileSystemStore
> ---------------------------------------
>                 Key: HADOOP-3506
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3506
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.17.0
>            Reporter: Robert
>            Assignee: Tom White
>             Fix For: 0.19.0
>         Attachments: hadoop-3506.patch
> In extraordinary circumstances (eg. S3 outages), calling S3FileSystem functions will
throw NullPointerExceptions when trying to read from the filesystem. I've traced this down
to calls to Jets3tFileSystemStore.get().
> Both get() functions catch an S3ServiceException, and check its error code using a string
comparison. However, the underlying libs3t library will sometimes produce an exception with
a null error code string. This results in an NPE that propagates all the way to the S3FileSystem,
and to the caller.
> To fix this, Jets3tFileSystemStore lines 196 and 212 should be changed from:
> bq.         if (e.getS3ErrorCode().equals("NoSuchKey")) {
> to:
> bq.         if ("NoSuchKey".equals(e.getS3ErrorCode())) {

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message