hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14215) DynamoDB client should waitForActive on existing tables
Date Fri, 07 Apr 2017 23:45:41 GMT

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

Sean Mackrory commented on HADOOP-14215:

Note for anyone seeing this JIRA in git history: I screwed up pushing HADOOP-14288. It ended
up with a commit message intended for this JIRA, and got mixed in with bits of my wip for
HADOOP-14068. I just went ahead and reverted the commit in question to cleanly apply HADOOP-14288
exactly as submitted to that JIRA.

> DynamoDB client should waitForActive on existing tables
> -------------------------------------------------------
>                 Key: HADOOP-14215
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14215
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Critical
>             Fix For: HADOOP-13345
>         Attachments: HADOOP-14215-HADOOP-13345.000.patch, HADOOP-14215-HADOOP-13345.001.patch,
> I saw a case where 2 separate applications tried to use the same non-pre-existing table
with table.create = true at about the same time. One failed with a ResourceInUse exception.
If a table does not exist, we attempt to create it and then wait for it to enter the active
state. If another jumps in in the middle of that, the table may exist, thus bypassing our
call to waitForActive(), and then try to use the table immediately.
> While we're at it, let's also make sure that the race condition where a table might get
created between checking if it exists and attempting to create it is handled gracefully.

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