-
Type:
Sub-task
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.2.0
-
Component/s: fs/s3
-
Labels:None
-
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
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
- is duplicated by
-
HADOOP-14576 s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection
-
- Resolved
-
- is related to
-
HADOOP-14576 s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection
-
- Resolved
-