[
https://issues.apache.org/jira/browse/HADOOP-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960084#comment-15960084
]
Mingliang Liu commented on HADOOP-14215:
----------------------------------------
Thanks so much [~mackrorysd]!
I checked the test in the new patch and it makes great sense for the testing. I
can also pass the test during multiple runs.
I'm myself +1 on the joint effort v2 patch. I'll commit this week if [~fabbri]
or [[email protected]] do not object.
> 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
> Attachments: HADOOP-14215-HADOOP-13345.000.patch,
> HADOOP-14215-HADOOP-13345.001.patch, HADOOP-14215-HADOOP-13345.002.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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
