[
https://issues.apache.org/jira/browse/HADOOP-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060628#comment-16060628
]
Steve Loughran commented on HADOOP-14576:
-----------------------------------------
# do you think this is something to need for an initial preview?
# how long does it go into this state —can we spin until it is fixed?
# For non-auth read, we could recover just by going to S3. For auth we don't
have that luxury.
Recommend adding an instrumentation field to count how often this happens;
would be useful in production to identify why delays were arising
> DynamoDB tables may leave 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: HADOOP-13345
> Reporter: Sean Mackrory
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]