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

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

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
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

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

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-15837-branch-3.1-004.patch
11/Oct/18 14:05
1 kB
Steve Loughran
HADOOP-15837-003.patch
11/Oct/18 14:04
10 kB
Steve Loughran
HADOOP-15837-002.patch
10/Oct/18 14:16
10 kB
Steve Loughran
HADOOP-15837-001.patch
09/Oct/18 22:08
10 kB
Steve Loughran

Issue Links

Add Link

is duplicated by

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

Resolved

Delete this link

is related to

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

Resolved

Delete this link

Activity

Comment

This comment will be Viewable by All Users Viewable by All Users

Cancel

People

Assignee:: Steve Loughran

Reporter:: Steve Loughran

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 09/Oct/18 20:56

Updated:: 24/May/19 17:24

Resolved:: 12/Oct/18 08:50

Agile

Slack

Issue deployment