[
https://issues.apache.org/jira/browse/HADOOP-16442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890148#comment-16890148
]
Steve Loughran commented on HADOOP-16442:
-----------------------------------------
in HADOOP-15183 there's a change in S3GuardTool.destroy command; we map a
timeout in waitForTable deletion to a new {{TableDeleteTimeoutException}} (
HADOOP-16364) , then in the tool catch and downgrade to a debug, on the basis
that "it's just AWS taking its time"
Should our test be spinning a bit here for those test runs where AWS takes too
long to delete a table?
> Intermittent failure of ITestS3GuardToolDynamoDB#testDynamoDBInitDestroyCycle
> -----------------------------------------------------------------------------
>
> Key: HADOOP-16442
> URL: https://issues.apache.org/jira/browse/HADOOP-16442
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Gabor Bota
> Priority: Minor
>
> ITestS3GuardToolDynamoDB#testDynamoDBInitDestroyCycle test is failing
> itermittently against ireland with the following stacktrace:
> {noformat}
> [ERROR] Tests run: 17, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 248.895 s <<< FAILURE! - in
> org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB
> [ERROR]
> testDynamoDBInitDestroyCycle(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB)
> Time elapsed: 141.461 s <<< FAILURE!
> java.lang.AssertionError: s3guard.test.testDynamoDBInitDestroy912421434 still
> exists
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at
> org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolDynamoDB.testDynamoDBInitDestroyCycle(ITestS3GuardToolDynamoDB.java:250)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
