[
https://issues.apache.org/jira/browse/HADOOP-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647673#comment-16647673
]
Steve Loughran commented on HADOOP-14576:
-----------------------------------------
we're now treating UPDATING as valid on startup, as it is possible to use when
its just a capacity adjustment. If repartitioning is different, then we need to
identify that error and use it for the retries of all operations, idempotent or
not.
Probably good to review all DDB exception [error
codes|https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html]
and make sure that the retryable ones are retried in all circumstances.
> s3guard DynamoDB resource not found: tables not ACTIVE state after initial
> connection
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-14576
> URL: https://issues.apache.org/jira/browse/HADOOP-14576
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Sean Mackrory
> Priority: Major
>
> 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...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
