[
https://issues.apache.org/jira/browse/HADOOP-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu resolved HADOOP-14215.
------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: HADOOP-13345
Committed to feature branch. Thanks for your contribution [~mackrorysd]. Thanks
[~fabbri] for review and [~rajesh.balamohan] for offline discussion.
> 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, 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: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
