[HADOOP-14576] s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.0-beta1
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Sean Mackrory
• Created: 22/Jun/17 22:12
• Updated: 24/May/19 17:24
• Resolved: 24/May/19 17:24

Description

We currently only anticipate tables not being in the ACTIVE state when first connecting. It is possible for a table to be in the ACTIVE state and move to an UPDATING state during partitioning events. Attempts to read or write during that time will result in an AmazonServerException getting thrown. We should try to handle that better...

Issue Links

• duplicates: HADOOP-15837 DynamoDB table Update can fail S3A FS init
• is blocked by: HADOOP-13761 S3Guard: implement retries for DDB failures and throttling; translate exceptions
• is depended upon by: HADOOP-14936 S3Guard: remove "experimental" from documentation
• relates to: HADOOP-15837 DynamoDB table Update can fail S3A FS init