[HADOOP-15837] DynamoDB table Update can fail S3A FS init

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.0
• Fix Version/s: 2.10.0, 3.2.0, 3.0.4, 3.1.2
• Component/s: fs/s3

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

• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 09/Oct/18 20:56
• Updated: 24/May/19 17:24
• Resolved: 12/Oct/18 08:50

Description

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

Issue Links

• is duplicated by: HADOOP-14576 s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection
• is related to: HADOOP-14576 s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection