You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/10/29 19:55:05 UTC
[jira] [Assigned] (HADOOP-13059) S3a over-reacts to potentially
transient network problems in its init() logic
[ https://issues.apache.org/jira/browse/HADOOP-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran reassigned HADOOP-13059:
---------------------------------------
Assignee: (was: Steve Loughran)
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org