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 "Gabor Bota (JIRA)" <ji...@apache.org> on 2018/07/04 14:18:00 UTC
[jira] [Commented] (HADOOP-15349) S3Guard DDB retryBackoff to be
more informative on limits exceeded
[ https://issues.apache.org/jira/browse/HADOOP-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532811#comment-16532811 ]
Gabor Bota commented on HADOOP-15349:
-------------------------------------
Hi [~stevel@apache.org],
I'm not able to find this test you running in the upstream/trunk. Could you send me the test you are running or the test is there somewhere, but I'm not able to find it?
> S3Guard DDB retryBackoff to be more informative on limits exceeded
> ------------------------------------------------------------------
>
> Key: HADOOP-15349
> URL: https://issues.apache.org/jira/browse/HADOOP-15349
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Major
> Attachments: failure.log
>
>
> When S3Guard can't update the DB and so throws an IOE after the retry limit is exceeded, it's not at all informative. Improve logging & exception
--
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