You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/06/14 09:13:00 UTC
[jira] [Comment Edited] (HADOOP-16375)
ITestS3AMetadataPersistenceException failure
[ https://issues.apache.org/jira/browse/HADOOP-16375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863865#comment-16863865 ]
Steve Loughran edited comment on HADOOP-16375 at 6/14/19 9:12 AM:
------------------------------------------------------------------
Stack is the exception crated in the setup; parameter is failOnError = false.
Conclusion: even though failOnError == false, the null metastore did raise the exception and it was passed all the way up. Which means the FS instance raised the exception even though the config said no
{code}
[ERROR] testFailedMetadataUpdate[1](org.apache.hadoop.fs.s3a.ITestS3AMetadataPersistenceException) Time elapsed: 1.193 s <<< ERROR!
java.io.IOException
at org.apache.hadoop.fs.s3a.ITestS3AMetadataPersistenceException.setup(ITestS3AMetadataPersistenceException.java:87)
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.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}
Hypothesis: the FS used in the test was the one cached from the previous run, so it had the old setting
Proposal: a new filesystem is created and closed for each test run
also advised: we clear the bucket options in case someone has been changing them in their site config
was (Author: stevel@apache.org):
Stack is the exception crated in the setup; parameter is failOnError = false.
Conclusion: even though failOnError == false, the null metastore did raise the exception. Which means the FS instance raised the exception even though the config said no
{code}
[ERROR] testFailedMetadataUpdate[1](org.apache.hadoop.fs.s3a.ITestS3AMetadataPersistenceException) Time elapsed: 1.193 s <<< ERROR!
java.io.IOException
at org.apache.hadoop.fs.s3a.ITestS3AMetadataPersistenceException.setup(ITestS3AMetadataPersistenceException.java:87)
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.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}
Hypothesis: the FS used in the test was the one cached from the previous run, so it had the old setting
Proposal: a new filesystem is created and closed for each test run
> ITestS3AMetadataPersistenceException failure
> --------------------------------------------
>
> Key: HADOOP-16375
> URL: https://issues.apache.org/jira/browse/HADOOP-16375
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Encountered on a s3guard, dynamo +auth parallel 8 thread test run:
> {code}
> [ERROR] testFailedMetadataUpdate[1](org.apache.hadoop.fs.s3a.ITestS3AMetadataPersistenceException)
> {code}
> didn't resurface on a standalone test
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org