[
https://issues.apache.org/jira/browse/HADOOP-18587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655099#comment-17655099
]
ASF GitHub Bot commented on HADOOP-18587:
-----------------------------------------
pjfanning commented on PR #5270:
URL: https://github.com/apache/hadoop/pull/5270#issuecomment-1372610396
@cnauroth there are still 2 test failures and they seem genuine (not
intermittent failures).
I might need someone with more HDFS debugging experience than me to look
into this one.
This test just timeouts waiting for a name-node restart. Something behind
the scenes is failing and not logging anything.
```
[INFO] Running
org.apache.hadoop.hdfs.TestErasureCodingPolicyWithSnapshotWithRandomECPolicy
[ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
149.393 s <<< FAILURE! - in
org.apache.hadoop.hdfs.TestErasureCodingPolicyWithSnapshotWithRandomECPolicy
[ERROR]
testSnapshotsOnErasureCodingDirAfterNNRestart(org.apache.hadoop.hdfs.TestErasureCodingPolicyWithSnapshotWithRandomECPolicy)
Time elapsed: 120.166 s <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 120000
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hdfs.MiniDFSCluster.waitActive(MiniDFSCluster.java:2831)
at
org.apache.hadoop.hdfs.MiniDFSCluster.restartNameNode(MiniDFSCluster.java:2320)
at
org.apache.hadoop.hdfs.MiniDFSCluster.restartNameNode(MiniDFSCluster.java:2271)
at
org.apache.hadoop.hdfs.TestErasureCodingPolicyWithSnapshot.testSnapshotsOnErasureCodingDirAfterNNRestart(TestErasureCodingPolicyWithSnapshot.java:174)
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:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
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.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:750)
```
Likewise, the mapreduce test failure has no obvious cause.
> upgrade to jettison 1.5.2 due to security issue
> -----------------------------------------------
>
> Key: HADOOP-18587
> URL: https://issues.apache.org/jira/browse/HADOOP-18587
> Project: Hadoop Common
> Issue Type: Task
> Components: common
> Reporter: PJ Fanning
> Priority: Major
> Labels: pull-request-available
>
> [https://github.com/advisories/GHSA-x27m-9w8j-5vcw]
>
> [https://github.com/jettison-json/jettison/releases]
> v1.5.2 is flagged as fixing a CVE but a v1.5.3 was quickly released and
> appears ti fix some regressions caused by v1.5.2.
> Many hadoop tests fail when jettison 1.5.2 is used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
