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] [Updated] (HADOOP-13059) S3a over-reacts to potentially transient network problems in its init() logic
Date Wed, 27 Apr 2016 10:23:13 GMT

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

Steve Loughran updated HADOOP-13059:
------------------------------------
    Priority: Minor  (was: Major)

> S3a over-reacts to potentially transient network problems in its init() logic
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-13059
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13059
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-13059-001.patch
>
>
> If there's a reason for s3a not being able to connect to AWS, then the constructor fails,
even if this is a potentially transient event.
> This happens because the code to check for a bucket existing will relay the exceptions.
> The constructor should catch IOEs against the remote FS, downgrade to warn and let the
code continue; it may fail later, but it may also recover.



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

Mime
View raw message