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/09 22:09:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Steve Loughran updated HADOOP-15837:
------------------------------------
    Attachment: HADOOP-15837-001.patch

> 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
>
>
> 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