hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14576) DynamoDB tables may leave ACTIVE state after initial connection
Date Fri, 01 Sep 2017 14:26:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150616#comment-16150616

Steve Loughran commented on HADOOP-14576:

DDB can -> updating after you change the capacity (as HADOOP-14220 will let you do). The
retry handler needs to recognise the special case of update-in-progress and have a long retry
for it

> 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: 3.0.0-beta1
>            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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message