You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2017/03/22 21:20:42 UTC

[jira] [Created] (HADOOP-14215) DynamoDB client should waitForActive on existing tables

Sean Mackrory created HADOOP-14215:
--------------------------------------

             Summary: 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
            Reporter: Sean Mackrory
            Assignee: Sean Mackrory


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
(v6.3.15#6346)

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