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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/02/10 10:09:35 UTC

[jira] [Resolved] (HADOOP-10737) S3n silent failure on copy, data loss on rename

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

Steve Loughran resolved HADOOP-10737.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.5.0
         Assignee: Steve Loughran

was fixed in 2.5.0 via the HADOOP-9961 patch

> S3n silent failure on copy, data loss on rename
> -----------------------------------------------
>
>                 Key: HADOOP-10737
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10737
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.4.0
>            Reporter: Gian Merlino
>            Assignee: Steve Loughran
>             Fix For: 2.5.0
>
>
> Jets3tNativeFileSystemStore.copy(String, String) handles its exceptions with handleServiceException(String, ServiceException), which behaves like:
> 1) Throw FileNotFoundException if the exception's error code is NoSuchKey
> 2) Otherwise, throw IOException if the exception's cause is an IOException
> 3) Otherwise, LOG.debug a message and throw nothing
> So S3 exceptions other than NoSuchKey (like RequestTimeout, ServiceUnavailable) are suppressed. This makes "copy" fail while still returning as if it succeeded. Furthermore since NativeS3FileSystem's "rename" is implemented as a copy followed by a delete, this means "rename" can delete the source key even though the copy has failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)