[
https://issues.apache.org/jira/browse/HADOOP-15837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644105#comment-16644105
]
Steve Loughran commented on HADOOP-15837:
-----------------------------------------
Proposed fix
waitForTableActive wrapped with retry; the failure to exit state triggers this.
Docs updated.
Give that the table still seems live (AWS Docs confirm this):
https://docs.amazonaws.cn/en_us/amazondynamodb/latest/developerguide/WorkingWithTables.Basics.html#WorkingWithTables.Basics.UpdateTable
the core solution is simple: update == ready to read.
I still want to add some retry checks on waitForTable though, in case the time
to come up is > built in wait time, which is clearly pretty small
> 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
>
> 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
