[
https://issues.apache.org/jira/browse/HADOOP-16407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877178#comment-16877178
]
Steve Loughran commented on HADOOP-16407:
-----------------------------------------
This is triggering now that in HADOOP-16384 I moved those tests which start MR
jobs into the sequential phase. That helps stop overload of the test system
through a spawn of too many processes (mini YARN cluster + MR job) per test
suite, but seems to be triggering recycling problems
{code}
[INFO] Running
org.apache.hadoop.fs.s3a.commit.staging.integration.ITestPartitionCommitMRJob
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.407 s
<<< FAILURE! - in
org.apache.hadoop.fs.s3a.commit.staging.integration.ITestPartitionCommitMRJob
[ERROR]
testMRJob(org.apache.hadoop.fs.s3a.commit.staging.integration.ITestPartitionCommitMRJob)
Time elapsed: 0.442 s <<< FAILURE!
java.lang.AssertionError: AWS client is not inconsistent, even though the test
requirees it com.amazonaws.services.s3.AmazonS3Client@13d0b3d
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.hadoop.fs.s3a.commit.AbstractCommitITest.setup(AbstractCommitITest.java:173)
at
org.apache.hadoop.fs.s3a.commit.AbstractYarnClusterITest.setup(AbstractYarnClusterITest.java:178)
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.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
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)
{code}
> Improve isolation of FS instances in S3A committer tests
> --------------------------------------------------------
>
> Key: HADOOP-16407
> URL: https://issues.apache.org/jira/browse/HADOOP-16407
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Major
>
> Filesystem recycling stops the ITest*Committer tests working all the time, if
> they pick up an existing FS which has a consistent instance.
> We can do better here
> Options
> * Base {{AbstractCommitITest}} creates both consistent and inconsistent
> filesystems, *does not destroy either, ever*, subclasses choose which to bond
> to
> * test setup to force disableFilesystemCaching(conf) in config setup; tear
> down to probe the FS for this option, and if true, close the FS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
