[jira] [Commented] (HADOOP-15627) S3A ITests failing if bucket explicitly set to s3guard+DDB
[ https://issues.apache.org/jira/browse/HADOOP-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554734#comment-16554734 ] Steve Loughran commented on HADOOP-15627: - Fixing in the HADOOP-15583 branch, as that's where I'm seeing these. It's coincidental, but > S3A ITests failing if bucket explicitly set to s3guard+DDB > -- > > Key: HADOOP-15627 > URL: https://issues.apache.org/jira/browse/HADOOP-15627 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test >Affects Versions: 3.2.0 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Repeatable failure in {{ITestS3GuardWriteBack.testListStatusWriteBack}} > Possible causes could include > * test not setting up the three fs instances > * (disabled) caching not isolating properly > * something more serious -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15627) S3A ITests failing if bucket explicitly set to s3guard+DDB
[ https://issues.apache.org/jira/browse/HADOOP-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554713#comment-16554713 ] Steve Loughran commented on HADOOP-15627: - latter test failure goes away if you increase the inconsistency time from the default 5s to 20s. That is: if your test run is slow enough, the inconsistencies will have expired and so the assertions fail. When your test bucket is on a different continent, your tests can become slow enough for this to surface > S3A ITests failing if bucket explicitly set to s3guard+DDB > -- > > Key: HADOOP-15627 > URL: https://issues.apache.org/jira/browse/HADOOP-15627 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test >Affects Versions: 3.2.0 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Repeatable failure in {{ITestS3GuardWriteBack.testListStatusWriteBack}} > Possible causes could include > * test not setting up the three fs instances > * (disabled) caching not isolating properly > * something more serious -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15627) S3A ITests failing if bucket explicitly set to s3guard+DDB
[ https://issues.apache.org/jira/browse/HADOOP-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553636#comment-16553636 ] Steve Loughran commented on HADOOP-15627: - I'm also seeing this {code} n: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.842 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.ITestS3GuardListConsistency [ERROR] testInconsistentS3ClientDeletes(org.apache.hadoop.fs.s3a.ITestS3GuardListConsistency) Time elapsed: 48.72 s <<< FAILURE! java.lang.AssertionError: InconsistentAmazonS3Client added back objects incorrectly in a non-recursive listing expected:<3> but was:<2> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.apache.hadoop.fs.s3a.ITestS3GuardListConsistency.testInconsistentS3ClientDeletes(ITestS3GuardListConsistency.java:528) 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:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) 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$StatementThread.run(FailOnTimeout.java:74) {code} FWIW, I'm running these tests against S3 Ireland + dynamo, but this time *from the US*. There will be different latencies. I worry that this is triggering the problems, as now we are seeing more real-world inconsistency or delays > S3A ITests failing if bucket explicitly set to s3guard+DDB > -- > > Key: HADOOP-15627 > URL: https://issues.apache.org/jira/browse/HADOOP-15627 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test >Affects Versions: 3.2.0 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Repeatable failure in {{ITestS3GuardWriteBack.testListStatusWriteBack}} > Possible causes could include > * test not setting up the three fs instances > * (disabled) caching not isolating properly > * something more serious -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15627) S3A ITests failing if bucket explicitly set to s3guard+DDB
[ https://issues.apache.org/jira/browse/HADOOP-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553631#comment-16553631 ] Steve Loughran commented on HADOOP-15627: - Similarly {code} ERROR] Tests run: 22, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 309.672 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolLocal [ERROR] testDiffCommand(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardToolLocal) Time elapsed: 29.885 s <<< FAILURE! java.lang.AssertionError: Mismatched metadata store outputs: S3 F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-0 MS F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-0 S3 F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-2 MS F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-2 S3 F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-3 MS F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-3 S3 F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-1 MS F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-1 S3 F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-4 MS F 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-4 MS D 0 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only MS F 100 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-3 MS F 100 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-2 MS F 100 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-4 MS F 100 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-0 MS F 100 s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-1 expected:<[s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-3, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-2, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-4, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-0, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-1]> but was:<[s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-3, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-0, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-2, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-4, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-2, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-0, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-3, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/ms_only/file-1, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-1, s3a://hwdev-steve-ireland-new/fork-0005/test/test-diff/s3_only/file-4]> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.apache.hadoop.fs.s3a.s3guard.AbstractS3GuardToolTestBase.testDiffCommand(AbstractS3GuardToolTestBase.java:449) 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:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) 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$StatementThread.run(FailOnTimeout.java:74) {code} > S3A ITests failing if bucket explicitly set to s3guard+DDB > -- > > Key: HADOOP-15627 > URL: https://issues.apache.org/jira/browse/HADOOP-15627 > Project: Hadoop Common >