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 "Sean Mackrory (JIRA)" <ji...@apache.org> on 2018/10/11 00:15:00 UTC
[jira] [Comment Edited] (HADOOP-15837) DynamoDB table Update can
fail S3A FS init
[ https://issues.apache.org/jira/browse/HADOOP-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645750#comment-16645750 ]
Sean Mackrory edited comment on HADOOP-15837 at 10/11/18 12:14 AM:
-------------------------------------------------------------------
Thanks for the fix [~stevel@apache.org] - the problem and solution make sense.
Being a little nit-picky, but can we rename maybeUnwrap to something a little more descriptive like getNestedSDKException, and just call it once instead of twice? There's a lot of exception translation going on and I think that'd make a big difference to understandability of this code.
Other than that I'm a +1. I did not get a chance to run tests myself today, but feel free to commit before I do since you have.
was (Author: mackrorysd):
Thanks for the fix [~stevel@apache.org] - the problem and solution make sense.
Being a little nit-picky, but can we rename maybeUnwrap to something a little more descriptive like getNestedSDKException, and just call it once instead of twice?
Other than that I'm a +1. I did not get a chance to run tests myself today, but feel free to commit before I do since you have.
> DynamoDB table Update can fail S3A FS init
> ------------------------------------------
>
> Key: HADOOP-15837
> URL: https://issues.apache.org/jira/browse/HADOOP-15837
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Environment: s3guard test with small capacity (10) but autoscale enabled & multiple consecutive parallel test runs executed...this seems to have been enough load to trigger the state change
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Attachments: HADOOP-15837-001.patch, HADOOP-15837-002.patch
>
>
> When DDB autoscales a table, it goes into an UPDATING state. The waitForTableActive operation in the AWS SDK doesn't seem to wait long enough for this to recover. We need to catch & retry
--
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