[
https://issues.apache.org/jira/browse/HADOOP-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076792#comment-16076792
]
Steve Loughran commented on HADOOP-14576:
-----------------------------------------
this parallel rename -it is how hive implements a commit? As if so, if we can
move it off rename/(copy & delete) as its commit strategy, then that could make
it go away.
Assuming it is a commit operation, we would presumably like it to complete,
even if that took 1+ attempt to go through. Which means: something which should
be retried.
I'm adding retry policy in the HADOOP-13786 commit code (and more fault
injection into the inconsistent client); we can use its handling and tests as a
basis for this. That branch/patch handles 503 throttled responses from S3 with
backoff and retry (and a shorter policy for other failures considered
recoverable)....DDB state changes could be treated as another error to handle
under the throttle policy.
> 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]