hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13059) S3a over-reacts to potentially transient network problems in its init() logic
Date Thu, 07 Sep 2017 09:52:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156757#comment-16156757
] 

Hadoop QA commented on HADOOP-13059:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} | {color:red}
HADOOP-13059 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-13059 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12800992/HADOOP-13059-001.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/13187/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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
>            Assignee: 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.4.14#64029)

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


Mime
View raw message