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 2017/09/01 13:41:01 UTC
[jira] [Resolved] (HADOOP-14810) S3Guard: handle provisioning
failure through backoff & retry (& metrics)
[ https://issues.apache.org/jira/browse/HADOOP-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-14810.
-------------------------------------
Resolution: Duplicate
Duplicate of HADOOP-13761; closing as such and pasting stack trace into that JIRA
> S3Guard: handle provisioning failure through backoff & retry (& metrics)
> ------------------------------------------------------------------------
>
> Key: HADOOP-14810
> URL: https://issues.apache.org/jira/browse/HADOOP-14810
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
> Attachments: summary.txt
>
>
> S3Guard can't handle overloaded tables.
> I think we all though the API did: it doesn't; exceptions get raised and the caller is expected to handle it.
> This relates very much to the s3a-lambda invocation code in HADOOP-13786 to handle failures during commit, and the need for all the S3AFileSystem calls of the S3 APIs to handle transient failures like throttling, and again, needs some fault injection to verify the handling, metrics to count rate so it can be monitored & used to understand why work is underperforming.
--
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