[
https://issues.apache.org/jira/browse/HADOOP-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646492#comment-16646492
]
Hudson commented on HADOOP-15837:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15179 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15179/])
HADOOP-15837. DynamoDB table Update can fail S3A FS init. Contributed by
(stevel: rev ee816f1fd78b029b9efa567e8b1b62391563de14)
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/DynamoDBMetadataStore.java
* (add)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/TestDynamoDBMiscOperations.java
> 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,
> HADOOP-15837-003.patch, HADOOP-15837-branch-3.1-004.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: [email protected]
For additional commands, e-mail: [email protected]
