[
https://issues.apache.org/jira/browse/HADOOP-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646814#comment-16646814
]
Steve Loughran commented on HADOOP-14576:
-----------------------------------------
The Updating issue is fixed by HADOOP-15837; its just recognised as a
functional state.
no idea about resource not found. My guess, that test had newly recreated a
deleted table, and assuming DDB's table index is eventually consistent, the app
got a delete marker
> 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]
