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) s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection
Date Thu, 02 Nov 2017 20:01:00 GMT

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

Steve Loughran commented on HADOOP-14576:
-----------------------------------------

We should recognise these DDB exceptions and treat as recoverable, at lest for a while. Interesting
that they are HTTP 400, not 404

> 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
(v6.4.14#64029)

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


Mime
View raw message