[
https://issues.apache.org/jira/browse/HADOOP-14733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114412#comment-16114412
]
Steve Loughran commented on HADOOP-14733:
-----------------------------------------
This happens repeatedly for me,
{code}
Table table = db.getTable(tableName);
table.waitForActive(); /// HERE
table.delete();
table.waitForDelete();
{code}
Given the table doesn't exist, should we just downgrade this in the test to
"allowed"; it's clear that the table has been deleted. What about just catch
the RNFE and consider it a successful outcome?
Note: this doesn't occur against real DDB (-Ddynamo) tests
> ITestS3GuardConcurrentOps failing with -Ddynamodblocal -Ds3guard
> ----------------------------------------------------------------
>
> Key: HADOOP-14733
> URL: https://issues.apache.org/jira/browse/HADOOP-14733
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
>
> Test failure with local ddb server for s3guard
> {code}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 128.876 sec
> <<< FAILURE! - in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardConcurrentOps
> testConcurrentTableCreations(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardConcurrentOps)
> Time elapsed: 128.785 sec <<< ERROR!
> com.amazonaws.services.dynamodbv2.model.ResourceNotFoundException: Cannot do
> operations on a non-existent table (Service: AmazonDynamoDBv2; Status Code:
> 400; Error Code: ResourceNotFoundException; Request ID:
> 82dbf479-3ec1-40fa-bd5c-ca0f206685e7)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
