[ https://issues.apache.org/jira/browse/HADOOP-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-15837: ------------------------------------ Resolution: Fixed Fix Version/s: 3.1.2 3.0.4 3.2.0 2.10.0 Status: Resolved (was: Patch Available) The 3.1-patch has gone back into all the branches with S3Guard in; closing as fixed > 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 > Fix For: 2.10.0, 3.2.0, 3.0.4, 3.1.2 > > 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org