hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-16490) S3GuardExistsRetryPolicy handle FNFE eventual consistency better
Date Mon, 05 Aug 2019 15:37:00 GMT
Steve Loughran created HADOOP-16490:

             Summary: S3GuardExistsRetryPolicy handle FNFE eventual consistency better
                 Key: HADOOP-16490
                 URL: https://issues.apache.org/jira/browse/HADOOP-16490
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
    Affects Versions: 3.3.0
            Reporter: Steve Loughran
            Assignee: Steve Loughran

If S3Guard is encountering delayed consistency (FNFE from tombstone; failure to open file)
* it only retries with the same times as everything else. We should make it differently configurable
* when an FNFE is finally thrown, rename() treats it as being caused by the original source
path missing, when in fact its something else. Proposed: somehow propagate the failure up
differently, probably in the S3AFileSystem.copyFile() code

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message