[jira] [Commented] (HADOOP-17331) [JDK 15] TestDNS fails by UncheckedIOException
[
https://issues.apache.org/jira/browse/HADOOP-17331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317814#comment-17317814
]
Akira Ajisaka commented on HADOOP-17331:
In Java 16, the error is reduced to 2
{quote}
[ERROR] Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.316
s <<< FAILURE! - in org.apache.hadoop.net.TestDNS
[ERROR] testLookupWithoutHostsFallback(org.apache.hadoop.net.TestDNS) Time
elapsed: 0.007 s <<< ERROR!
java.lang.NoSuchFieldException: modifiers
at java.base/java.lang.Class.getDeclaredField(Class.java:2549)
at
org.apache.hadoop.net.TestDNS.changeDnsCachedHostname(TestDNS.java:251)
at
org.apache.hadoop.net.TestDNS.testLookupWithoutHostsFallback(TestDNS.java:222)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
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.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:831)
[ERROR] testLookupWithHostsFallback(org.apache.hadoop.net.TestDNS) Time
elapsed: 0.002 s <<< ERROR!
java.lang.NoSuchFieldException: modifiers
at java.base/java.lang.Class.getDeclaredField(Class.java:2549)
at
org.apache.hadoop.net.TestDNS.changeDnsCachedHostname(TestDNS.java:251)
at
org.apache.hadoop.net.TestDNS.testLookupWithHostsFallback(TestDNS.java:200)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
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.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:831)
{quote}
> [JDK 15] TestDNS fails by UncheckedIOException
> --
>
> Key: HADOOP-17331
> URL: https://issues.apache.org/jira/browse/HADOOP-17331
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Priority: Major
>
> After [JDK-8235783|https://bugs.openjdk.java.net/browse/JDK-8235783],
> DatagramSocket::connect throws UncheckedIOException if connect fails.
> {noformat}
> [INFO] Running org.apache.hadoop.net.TestDNS
> [ERROR] Tests run: 12, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 0.403 s <<< FAILURE! - in org.apache.hadoop.net.TestDNS
> [ERROR] testNullDnsServer(org.apache.hadoop.net.TestDNS) Time elapsed: 0.134
> s <<< ERROR!
> java.io.UncheckedIOException: java.net.SocketException: Unsupported address
> type
> at
> java.base/sun.nio.ch.DatagramSocketAdaptor.connect(DatagramSocketAdaptor.java:120)
> at java.base/java.net.DatagramSocket.connect(DatagramSocket.java:341)
> {noformat}
> Full error log:
> https://gist.github.com/aajisaka/2a24cb2b110cc3d19f7dec6256db6844
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17331) [JDK 15] TestDNS fails by UncheckedIOException
[
https://issues.apache.org/jira/browse/HADOOP-17331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned HADOOP-17331:
--
Assignee: Akira Ajisaka
> [JDK 15] TestDNS fails by UncheckedIOException
> --
>
> Key: HADOOP-17331
> URL: https://issues.apache.org/jira/browse/HADOOP-17331
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> After [JDK-8235783|https://bugs.openjdk.java.net/browse/JDK-8235783],
> DatagramSocket::connect throws UncheckedIOException if connect fails.
> {noformat}
> [INFO] Running org.apache.hadoop.net.TestDNS
> [ERROR] Tests run: 12, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 0.403 s <<< FAILURE! - in org.apache.hadoop.net.TestDNS
> [ERROR] testNullDnsServer(org.apache.hadoop.net.TestDNS) Time elapsed: 0.134
> s <<< ERROR!
> java.io.UncheckedIOException: java.net.SocketException: Unsupported address
> type
> at
> java.base/sun.nio.ch.DatagramSocketAdaptor.connect(DatagramSocketAdaptor.java:120)
> at java.base/java.net.DatagramSocket.connect(DatagramSocket.java:341)
> {noformat}
> Full error log:
> https://gist.github.com/aajisaka/2a24cb2b110cc3d19f7dec6256db6844
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17331) [JDK 15] TestDNS fails by UncheckedIOException
[
https://issues.apache.org/jira/browse/HADOOP-17331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17331:
---
Status: Patch Available (was: Open)
> [JDK 15] TestDNS fails by UncheckedIOException
> --
>
> Key: HADOOP-17331
> URL: https://issues.apache.org/jira/browse/HADOOP-17331
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [JDK-8235783|https://bugs.openjdk.java.net/browse/JDK-8235783],
> DatagramSocket::connect throws UncheckedIOException if connect fails.
> {noformat}
> [INFO] Running org.apache.hadoop.net.TestDNS
> [ERROR] Tests run: 12, Failures: 0, Errors: 5, Skipped: 0, Time elapsed:
> 0.403 s <<< FAILURE! - in org.apache.hadoop.net.TestDNS
> [ERROR] testNullDnsServer(org.apache.hadoop.net.TestDNS) Time elapsed: 0.134
> s <<< ERROR!
> java.io.UncheckedIOException: java.net.SocketException: Unsupported address
> type
> at
> java.base/sun.nio.ch.DatagramSocketAdaptor.connect(DatagramSocketAdaptor.java:120)
> at java.base/java.net.DatagramSocket.connect(DatagramSocket.java:341)
> {noformat}
> Full error log:
> https://gist.github.com/aajisaka/2a24cb2b110cc3d19f7dec6256db6844
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17629) [JDK 16] TestRPC#testAuthorization fails by ClassCastException
Akira Ajisaka created HADOOP-17629:
--
Summary: [JDK 16] TestRPC#testAuthorization fails by
ClassCastException
Key: HADOOP-17629
URL: https://issues.apache.org/jira/browse/HADOOP-17629
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Akira Ajisaka
{quote}
[ERROR] testAuthorization(org.apache.hadoop.ipc.TestRPC) Time elapsed: 1.066 s
<<< ERROR!
java.lang.ClassCastException: class java.net.SocketException cannot be cast to
class org.apache.hadoop.ipc.RemoteException (java.net.SocketException is in
module java.base of loader 'bootstrap'; org.apache.hadoop.ipc.RemoteException
is in unnamed module of loader 'app')
at org.apache.hadoop.ipc.TestRPC.doRPCs(TestRPC.java:591)
at org.apache.hadoop.ipc.TestRPC.testAuthorization(TestRPC.java:639)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17630) [JDK 15] TestPrintableString fails due to Unicode 13.0 support
Akira Ajisaka created HADOOP-17630:
--
Summary: [JDK 15] TestPrintableString fails due to Unicode 13.0
support
Key: HADOOP-17630
URL: https://issues.apache.org/jira/browse/HADOOP-17630
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Akira Ajisaka
After [JDK-8239383|https://bugs.openjdk.java.net/browse/JDK-8239383], Unicode
13.0 is supported and TestPrintableString fails.
U+3 is actually used in Unicode 13.0:
https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_G
{quote}
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.055 s
<<< FAILURE! - in org.apache.hadoop.fs.shell.TestPrintableString
[ERROR]
testNonPrintableCharacters(org.apache.hadoop.fs.shell.TestPrintableString)
Time elapsed: 0.014 s <<< FAILURE!
java.lang.AssertionError:
Should replace unassigned U+3 and U+D
Expected: is "-?-?-"
but: was "-𰀀-?-"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:964)
at
org.apache.hadoop.fs.shell.TestPrintableString.expect(TestPrintableString.java:32)
at
org.apache.hadoop.fs.shell.TestPrintableString.testNonPrintableCharacters(TestPrintableString.java:79)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17630) [JDK 15] TestPrintableString fails due to Unicode 13.0 support
[
https://issues.apache.org/jira/browse/HADOOP-17630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17630:
---
Target Version/s: 3.3.1, 3.4.0
Assignee: Akira Ajisaka
Status: Patch Available (was: Open)
> [JDK 15] TestPrintableString fails due to Unicode 13.0 support
> --
>
> Key: HADOOP-17630
> URL: https://issues.apache.org/jira/browse/HADOOP-17630
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: newbie, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After [JDK-8239383|https://bugs.openjdk.java.net/browse/JDK-8239383], Unicode
> 13.0 is supported and TestPrintableString fails.
> U+3 is actually used in Unicode 13.0:
> https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_G
> {quote}
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.055
> s <<< FAILURE! - in org.apache.hadoop.fs.shell.TestPrintableString
> [ERROR]
> testNonPrintableCharacters(org.apache.hadoop.fs.shell.TestPrintableString)
> Time elapsed: 0.014 s <<< FAILURE!
> java.lang.AssertionError:
> Should replace unassigned U+3 and U+D
> Expected: is "-?-?-"
> but: was "-𰀀-?-"
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:964)
> at
> org.apache.hadoop.fs.shell.TestPrintableString.expect(TestPrintableString.java:32)
> at
> org.apache.hadoop.fs.shell.TestPrintableString.testNonPrintableCharacters(TestPrintableString.java:79)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17608) Fix TestKMS failure
[
https://issues.apache.org/jira/browse/HADOOP-17608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17608:
---
Summary: Fix TestKMS failure (was: TestKMS is flaky)
> Fix TestKMS failure
> ---
>
> Key: HADOOP-17608
> URL: https://issues.apache.org/jira/browse/HADOOP-17608
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: flaky-test, pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> [https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/460/artifact/out/patch-unit-hadoop-common-project_hadoop-kms.txt]
> The following https tests are flaky:
> * testStartStopHttpsPseudo
> * testStartStopHttpsKerberos
> * testDelegationTokensOpsHttpsPseudo
> {noformat}
> [ERROR]
> testStartStopHttpsPseudo(org.apache.hadoop.crypto.key.kms.server.TestKMS)
> Time elapsed: 1.354 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$1.call(TestKMS.java:553)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$1.call(TestKMS.java:534)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:258)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:235)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:230)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testStartStop(TestKMS.java:534)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testStartStopHttpsPseudo(TestKMS.java:634){noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17608) Fix TestKMS failure
[
https://issues.apache.org/jira/browse/HADOOP-17608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved HADOOP-17608.
Fix Version/s: 3.4.0
3.3.1
Resolution: Fixed
Merged #2880 into trunk and branch-3.3.
> Fix TestKMS failure
> ---
>
> Key: HADOOP-17608
> URL: https://issues.apache.org/jira/browse/HADOOP-17608
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: flaky-test, pull-request-available
> Fix For: 3.3.1, 3.4.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> [https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/460/artifact/out/patch-unit-hadoop-common-project_hadoop-kms.txt]
> The following https tests are flaky:
> * testStartStopHttpsPseudo
> * testStartStopHttpsKerberos
> * testDelegationTokensOpsHttpsPseudo
> {noformat}
> [ERROR]
> testStartStopHttpsPseudo(org.apache.hadoop.crypto.key.kms.server.TestKMS)
> Time elapsed: 1.354 s <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$1.call(TestKMS.java:553)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$1.call(TestKMS.java:534)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:258)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:235)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:230)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testStartStop(TestKMS.java:534)
> at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testStartStopHttpsPseudo(TestKMS.java:634){noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17630) [JDK 15] TestPrintableString fails due to Unicode 13.0 support
[
https://issues.apache.org/jira/browse/HADOOP-17630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17630:
---
Fix Version/s: 3.2.3
3.1.5
3.4.0
3.3.1
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-3.3, branch-3.2, and branch-3.1.
> [JDK 15] TestPrintableString fails due to Unicode 13.0 support
> --
>
> Key: HADOOP-17630
> URL: https://issues.apache.org/jira/browse/HADOOP-17630
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: newbie, pull-request-available
> Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> After [JDK-8239383|https://bugs.openjdk.java.net/browse/JDK-8239383], Unicode
> 13.0 is supported and TestPrintableString fails.
> U+3 is actually used in Unicode 13.0:
> https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_G
> {quote}
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.055
> s <<< FAILURE! - in org.apache.hadoop.fs.shell.TestPrintableString
> [ERROR]
> testNonPrintableCharacters(org.apache.hadoop.fs.shell.TestPrintableString)
> Time elapsed: 0.014 s <<< FAILURE!
> java.lang.AssertionError:
> Should replace unassigned U+3 and U+D
> Expected: is "-?-?-"
> but: was "-𰀀-?-"
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:964)
> at
> org.apache.hadoop.fs.shell.TestPrintableString.expect(TestPrintableString.java:32)
> at
> org.apache.hadoop.fs.shell.TestPrintableString.testNonPrintableCharacters(TestPrintableString.java:79)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:567)
> 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17524) Remove EventCounter
[ https://issues.apache.org/jira/browse/HADOOP-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320616#comment-17320616 ] Akira Ajisaka commented on HADOOP-17524: [~vjasani] Yes, go ahead! > Remove EventCounter > --- > > Key: HADOOP-17524 > URL: https://issues.apache.org/jira/browse/HADOOP-17524 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Assignee: Viraj Jasani >Priority: Major > > EventCount is using Log4J 1.x API. We need to remove it to drop Log4J 1.x. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17524) Remove EventCounter and Log counters from JVM Metrics
[ https://issues.apache.org/jira/browse/HADOOP-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17524: --- Summary: Remove EventCounter and Log counters from JVM Metrics (was: Remove EventCounter) > Remove EventCounter and Log counters from JVM Metrics > - > > Key: HADOOP-17524 > URL: https://issues.apache.org/jira/browse/HADOOP-17524 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > EventCount is using Log4J 1.x API. We need to remove it to drop Log4J 1.x. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17524) Remove EventCounter and Log counters from JVM Metrics
[ https://issues.apache.org/jira/browse/HADOOP-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17524: --- Fix Version/s: 3.4.0 Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. > Remove EventCounter and Log counters from JVM Metrics > - > > Key: HADOOP-17524 > URL: https://issues.apache.org/jira/browse/HADOOP-17524 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > EventCount is using Log4J 1.x API. We need to remove it to drop Log4J 1.x. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17525) Remove GenericTestUtils.setLogLevel
[
https://issues.apache.org/jira/browse/HADOOP-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322066#comment-17322066
]
Akira Ajisaka commented on HADOOP-17525:
{quote}Do you think we should go with this change (with log4j2 in test
dependency) on trunk independently?
{quote}
Yes. Thank you for the comment.
> Remove GenericTestUtils.setLogLevel
> ---
>
> Key: HADOOP-17525
> URL: https://issues.apache.org/jira/browse/HADOOP-17525
> Project: Hadoop Common
> Issue Type: Sub-task
>Reporter: Akira Ajisaka
>Priority: Major
>
> GenericTestUtils.setLogLevel depends on Log4J 1.x API, and it should be
> removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17525) Support log4j2 API in GenericTestUtils.setLogLevel
[ https://issues.apache.org/jira/browse/HADOOP-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322070#comment-17322070 ] Akira Ajisaka commented on HADOOP-17525: Updated the title and the description. > Support log4j2 API in GenericTestUtils.setLogLevel > -- > > Key: HADOOP-17525 > URL: https://issues.apache.org/jira/browse/HADOOP-17525 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Priority: Major > > GenericTestUtils.setLogLevel depends on Log4J 1.x API, should be updated to > use Log4J 2.x API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17525) Support log4j2 API in GenericTestUtils.setLogLevel
[ https://issues.apache.org/jira/browse/HADOOP-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17525: --- Summary: Support log4j2 API in GenericTestUtils.setLogLevel (was: Remove GenericTestUtils.setLogLevel) > Support log4j2 API in GenericTestUtils.setLogLevel > -- > > Key: HADOOP-17525 > URL: https://issues.apache.org/jira/browse/HADOOP-17525 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Priority: Major > > GenericTestUtils.setLogLevel depends on Log4J 1.x API, and it should be > removed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17525) Support log4j2 API in GenericTestUtils.setLogLevel
[ https://issues.apache.org/jira/browse/HADOOP-17525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17525: --- Description: GenericTestUtils.setLogLevel depends on Log4J 1.x API, should be updated to use Log4J 2.x API. (was: GenericTestUtils.setLogLevel depends on Log4J 1.x API, and it should be removed.) > Support log4j2 API in GenericTestUtils.setLogLevel > -- > > Key: HADOOP-17525 > URL: https://issues.apache.org/jira/browse/HADOOP-17525 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Priority: Major > > GenericTestUtils.setLogLevel depends on Log4J 1.x API, should be updated to > use Log4J 2.x API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17635) Update the ubuntu version in the build instruction
Akira Ajisaka created HADOOP-17635:
--
Summary: Update the ubuntu version in the build instruction
Key: HADOOP-17635
URL: https://issues.apache.org/jira/browse/HADOOP-17635
Project: Hadoop Common
Issue Type: Bug
Components: build, documentation
Reporter: Akira Ajisaka
In BUILDING.txt
{noformat}
Installing required packages for clean install of Ubuntu 14.04 LTS Desktop:
{noformat}
Ubuntu 14 is already EoL, should be updated to 18 or 20.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17642) Remove appender EventCounter to avoid instantiation
[
https://issues.apache.org/jira/browse/HADOOP-17642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17642:
---
Summary: Remove appender EventCounter to avoid instantiation (was: Could
not instantiate class org.apache.hadoop.log.metrics.EventCounter)
> Remove appender EventCounter to avoid instantiation
>
>
> Key: HADOOP-17642
> URL: https://issues.apache.org/jira/browse/HADOOP-17642
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After removal of EventCounter class, we are not able to bring up HDFS cluster.
> {code:java}
> log4j:ERROR Could not instantiate class
> [org.apache.hadoop.log.metrics.EventCounter].
> java.lang.ClassNotFoundException: org.apache.hadoop.log.metrics.EventCounter
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:198)
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:327)
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:124)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:785)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at org.slf4j.impl.Log4jLoggerFactory.(Log4jLoggerFactory.java:66)
> at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:72)
> at
> org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:45)
> at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
> at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
> at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:417)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:362)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388)
> at org.apache.hadoop.conf.Configuration.(Configuration.java:229)
> at org.apache.hadoop.hdfs.tools.GetConf.(GetConf.java:131)
> log4j:ERROR Could not instantiate appender named "EventCounter".
> {code}
> We need to clean up log4j.properties to avoid instantiating appender
> EventCounter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17642) Remove appender EventCounter to avoid instantiation
[
https://issues.apache.org/jira/browse/HADOOP-17642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17642:
---
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk. Thank you [~vjasani]!
> Remove appender EventCounter to avoid instantiation
>
>
> Key: HADOOP-17642
> URL: https://issues.apache.org/jira/browse/HADOOP-17642
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After removal of EventCounter class, we are not able to bring up HDFS cluster.
> {code:java}
> log4j:ERROR Could not instantiate class
> [org.apache.hadoop.log.metrics.EventCounter].
> java.lang.ClassNotFoundException: org.apache.hadoop.log.metrics.EventCounter
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.apache.log4j.helpers.Loader.loadClass(Loader.java:198)
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:327)
> at
> org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:124)
> at
> org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:785)
> at
> org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
> at
> org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
> at
> org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
> at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
> at org.apache.log4j.LogManager.(LogManager.java:127)
> at org.slf4j.impl.Log4jLoggerFactory.(Log4jLoggerFactory.java:66)
> at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:72)
> at
> org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:45)
> at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
> at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
> at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:417)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:362)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388)
> at org.apache.hadoop.conf.Configuration.(Configuration.java:229)
> at org.apache.hadoop.hdfs.tools.GetConf.(GetConf.java:131)
> log4j:ERROR Could not instantiate appender named "EventCounter".
> {code}
> We need to clean up log4j.properties to avoid instantiating appender
> EventCounter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17432) [JDK 16] KerberosUtil#getOidInstance is broken by JEP 396
[
https://issues.apache.org/jira/browse/HADOOP-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324456#comment-17324456
]
Akira Ajisaka commented on HADOOP-17432:
bq. Is this change in the signature of a public method?
This class is not annotated {{@Public}}, so the method is not {{@Public}}. Hive
should not use this method.
bq. Marking it deprecated is of not much use now right?
Now this function is not worth keeping because direct use of
KerberosUtil.GSS_SPNEGO_MECH_OID is more efficient than calling
KerberosUtil.getOidInstance("GSS_SPNEGO_MECH_OID"). Therefore I deprecated it.
bq. Akira Ajisaka can we add the Exceptions back for compatibility keeping the
code inside same, This seems for JDK-16 only right?
Yes, we can add the exception back.
This issue occurs not only JDK 16 and also JDK 17 and upper.
> [JDK 16] KerberosUtil#getOidInstance is broken by JEP 396
> -
>
> Key: HADOOP-17432
> URL: https://issues.apache.org/jira/browse/HADOOP-17432
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: auth
> Environment: Java 16-ea+28
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> JEP 396 (Strongly Encapsulate JDK Internals by Default) has been migrated
> since Java 16 EA Build 28. Calling the internal APIs (except the critical
> APIs such as sun.misc.Unsafe) are banned by default.
> {noformat}
> [INFO] Running
> org.apache.hadoop.security.authentication.server.TestAltKerberosAuthenticationHandler
> [ERROR] Tests run: 16, Failures: 0, Errors: 2, Skipped: 0, Time elapsed:
> 17.323 s <<< FAILURE! - in
> org.apache.hadoop.security.authentication.server.TestAltKerberosAuthenticationHandler
> [ERROR]
> testNonDefaultNonBrowserUserAgentAsNonBrowser(org.apache.hadoop.security.authentication.server.TestAltKerberosAuthenticationHandler)
> Time elapsed: 1.272 s <<< ERROR!
> java.lang.IllegalAccessException: class
> org.apache.hadoop.security.authentication.util.KerberosUtil cannot access
> class sun.security.jgss.GSSUtil (in module java.security.jgss) because module
> java.security.jgss does not export sun.security.jgss to unnamed module
> @48967c8b
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:385)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:687)
> at java.base/java.lang.reflect.Field.checkAccess(Field.java:1096)
> at java.base/java.lang.reflect.Field.get(Field.java:417)
> at
> org.apache.hadoop.security.authentication.util.KerberosUtil.getOidInstance(KerberosUtil.java:90)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17644) Add back the exceptions removed by HADOOP-17432 for compatibility
Akira Ajisaka created HADOOP-17644: -- Summary: Add back the exceptions removed by HADOOP-17432 for compatibility Key: HADOOP-17644 URL: https://issues.apache.org/jira/browse/HADOOP-17644 Project: Hadoop Common Issue Type: Bug Components: bulid Reporter: Akira Ajisaka As [~ayushsaxena] commented in https://issues.apache.org/jira/browse/HADOOP-17432?focusedCommentId=17324284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17324284, we need to add back the exceptions for compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17524) Remove EventCounter and Log counters from JVM Metrics
[ https://issues.apache.org/jira/browse/HADOOP-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324457#comment-17324457 ] Akira Ajisaka commented on HADOOP-17524: For this feature, there are no compatible way to upgrade to log4j2 because EventCounter extends org.apache.log4j.AppenderSkelton. The ideal way is to deprecate in Hadoop 3.4 and remove in Hadoop 4.0, but I think the plan takes too much time. > Remove EventCounter and Log counters from JVM Metrics > - > > Key: HADOOP-17524 > URL: https://issues.apache.org/jira/browse/HADOOP-17524 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Akira Ajisaka >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > EventCount is using Log4J 1.x API. We need to remove it to drop Log4J 1.x. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17644) Add back the exceptions removed by HADOOP-17432 for compatibility
[ https://issues.apache.org/jira/browse/HADOOP-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17644: -- Assignee: Quan Li > Add back the exceptions removed by HADOOP-17432 for compatibility > - > > Key: HADOOP-17644 > URL: https://issues.apache.org/jira/browse/HADOOP-17644 > Project: Hadoop Common > Issue Type: Bug > Components: bulid >Reporter: Akira Ajisaka >Assignee: Quan Li >Priority: Critical > > As [~ayushsaxena] commented in > https://issues.apache.org/jira/browse/HADOOP-17432?focusedCommentId=17324284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17324284, > we need to add back the exceptions for compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17644) Add back the exceptions removed by HADOOP-17432 for compatibility
[ https://issues.apache.org/jira/browse/HADOOP-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324569#comment-17324569 ] Akira Ajisaka commented on HADOOP-17644: Assigned. Thanks. > Add back the exceptions removed by HADOOP-17432 for compatibility > - > > Key: HADOOP-17644 > URL: https://issues.apache.org/jira/browse/HADOOP-17644 > Project: Hadoop Common > Issue Type: Bug > Components: bulid >Reporter: Akira Ajisaka >Assignee: Quan Li >Priority: Critical > > As [~ayushsaxena] commented in > https://issues.apache.org/jira/browse/HADOOP-17432?focusedCommentId=17324284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17324284, > we need to add back the exceptions for compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17644) Add back the exceptions removed by HADOOP-17432 for compatibility
[ https://issues.apache.org/jira/browse/HADOOP-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17644: --- Parent: HADOOP-17177 Issue Type: Sub-task (was: Bug) > Add back the exceptions removed by HADOOP-17432 for compatibility > - > > Key: HADOOP-17644 > URL: https://issues.apache.org/jira/browse/HADOOP-17644 > Project: Hadoop Common > Issue Type: Sub-task > Components: bulid >Reporter: Akira Ajisaka >Assignee: Quan Li >Priority: Critical > > As [~ayushsaxena] commented in > https://issues.apache.org/jira/browse/HADOOP-17432?focusedCommentId=17324284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17324284, > we need to add back the exceptions for compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17655) Upgrade Jetty to 9.4.40
Akira Ajisaka created HADOOP-17655:
--
Summary: Upgrade Jetty to 9.4.40
Key: HADOOP-17655
URL: https://issues.apache.org/jira/browse/HADOOP-17655
Project: Hadoop Common
Issue Type: Bug
Environment: Hadoop 3.3.0 + HDFS-17625 + many patches
Reporter: Akira Ajisaka
Jetty 9.4.39 has a critical bug:
https://github.com/eclipse/jetty.project/issues/6152
It causes http put failure in HttpFS.
{noformat}
curl --negotiate -u : "https://:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
Content-Type:application/octet-stream -T
curl: (55) TCP connection reset by peer
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17655) Upgrade Jetty to 9.4.40
[
https://issues.apache.org/jira/browse/HADOOP-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17655:
---
Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches (was: Hadoop 3.3.0
+ HDFS-17625 + many patches)
> Upgrade Jetty to 9.4.40
> ---
>
> Key: HADOOP-17655
> URL: https://issues.apache.org/jira/browse/HADOOP-17655
> Project: Hadoop Common
> Issue Type: Bug
> Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches
>Reporter: Akira Ajisaka
>Priority: Blocker
> Labels: release-blocker
>
> Jetty 9.4.39 has a critical bug:
> https://github.com/eclipse/jetty.project/issues/6152
> It causes http put failure in HttpFS.
> {noformat}
> curl --negotiate -u : "https:// host>:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
> Content-Type:application/octet-stream -T
> curl: (55) TCP connection reset by peer
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17655) Upgrade Jetty to 9.4.40
[
https://issues.apache.org/jira/browse/HADOOP-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17655:
---
Description:
Jetty 9.4.39 has a critical bug:
https://github.com/eclipse/jetty.project/issues/6152
It causes http put failure in HttpFS with SSL enabled.
{noformat}
curl --negotiate -u : "https://:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
Content-Type:application/octet-stream -T
curl: (55) TCP connection reset by peer
{noformat}
was:
Jetty 9.4.39 has a critical bug:
https://github.com/eclipse/jetty.project/issues/6152
It causes http put failure in HttpFS.
{noformat}
curl --negotiate -u : "https://:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
Content-Type:application/octet-stream -T
curl: (55) TCP connection reset by peer
{noformat}
> Upgrade Jetty to 9.4.40
> ---
>
> Key: HADOOP-17655
> URL: https://issues.apache.org/jira/browse/HADOOP-17655
> Project: Hadoop Common
> Issue Type: Bug
> Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches
>Reporter: Akira Ajisaka
>Priority: Blocker
> Labels: release-blocker
>
> Jetty 9.4.39 has a critical bug:
> https://github.com/eclipse/jetty.project/issues/6152
> It causes http put failure in HttpFS with SSL enabled.
> {noformat}
> curl --negotiate -u : "https:// host>:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
> Content-Type:application/octet-stream -T
> curl: (55) TCP connection reset by peer
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17655) Upgrade Jetty to 9.4.40
[
https://issues.apache.org/jira/browse/HADOOP-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17655:
---
Target Version/s: 3.3.1, 3.4.0, 3.1.5, 3.2.3 (was: 3.3.1, 3.4.0)
> Upgrade Jetty to 9.4.40
> ---
>
> Key: HADOOP-17655
> URL: https://issues.apache.org/jira/browse/HADOOP-17655
> Project: Hadoop Common
> Issue Type: Bug
> Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches
>Reporter: Akira Ajisaka
>Priority: Blocker
> Labels: pull-request-available, release-blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Jetty 9.4.39 has a critical bug:
> https://github.com/eclipse/jetty.project/issues/6152
> It causes http put failure in HttpFS with SSL enabled.
> {noformat}
> curl --negotiate -u : "https:// host>:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
> Content-Type:application/octet-stream -T
> curl: (55) TCP connection reset by peer
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17655) Upgrade Jetty to 9.4.40
[
https://issues.apache.org/jira/browse/HADOOP-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17655:
---
Assignee: Akira Ajisaka
Status: Patch Available (was: Open)
> Upgrade Jetty to 9.4.40
> ---
>
> Key: HADOOP-17655
> URL: https://issues.apache.org/jira/browse/HADOOP-17655
> Project: Hadoop Common
> Issue Type: Bug
> Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Blocker
> Labels: pull-request-available, release-blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Jetty 9.4.39 has a critical bug:
> https://github.com/eclipse/jetty.project/issues/6152
> It causes http put failure in HttpFS with SSL enabled.
> {noformat}
> curl --negotiate -u : "https:// host>:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
> Content-Type:application/octet-stream -T
> curl: (55) TCP connection reset by peer
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17655) Upgrade Jetty to 9.4.40
[
https://issues.apache.org/jira/browse/HADOOP-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17655:
---
Fix Version/s: 3.2.3
3.1.5
3.4.0
3.3.1
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-3.3, branch-3.2, and branch-3.1.
> Upgrade Jetty to 9.4.40
> ---
>
> Key: HADOOP-17655
> URL: https://issues.apache.org/jira/browse/HADOOP-17655
> Project: Hadoop Common
> Issue Type: Bug
> Environment: Hadoop 3.3.0 + HADOOP-17625 + many patches
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Blocker
> Labels: pull-request-available, release-blocker
> Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Jetty 9.4.39 has a critical bug:
> https://github.com/eclipse/jetty.project/issues/6152
> It causes http put failure in HttpFS with SSL enabled.
> {noformat}
> curl --negotiate -u : "https:// host>:/webhdfs/v1/?op=CREATE&data=true" -X PUT -H
> Content-Type:application/octet-stream -T
> curl: (55) TCP connection reset by peer
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17664) Web site release 3.2.2 changelog 404
[ https://issues.apache.org/jira/browse/HADOOP-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17664. Fix Version/s: asf-site Resolution: Fixed Merged the PR. > Web site release 3.2.2 changelog 404 > > > Key: HADOOP-17664 > URL: https://issues.apache.org/jira/browse/HADOOP-17664 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 3.3.0, 3.2.2 >Reporter: Jinpeng Chi >Priority: Trivial > Labels: pull-request-available > Fix For: asf-site > > Time Spent: 40m > Remaining Estimate: 0h > > Web site release changelog url 404 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17664) Web site release 3.2.2 changelog 404
[ https://issues.apache.org/jira/browse/HADOOP-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17664: -- Assignee: Jinpeng Chi > Web site release 3.2.2 changelog 404 > > > Key: HADOOP-17664 > URL: https://issues.apache.org/jira/browse/HADOOP-17664 > Project: Hadoop Common > Issue Type: Improvement > Components: documentation >Affects Versions: 3.3.0, 3.2.2 >Reporter: Jinpeng Chi >Assignee: Jinpeng Chi >Priority: Trivial > Labels: pull-request-available > Fix For: asf-site > > Time Spent: 40m > Remaining Estimate: 0h > > Web site release changelog url 404 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17664) Web site release 3.2.2 changelog 404
[ https://issues.apache.org/jira/browse/HADOOP-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17664: --- Issue Type: Bug (was: Improvement) Priority: Minor (was: Trivial) > Web site release 3.2.2 changelog 404 > > > Key: HADOOP-17664 > URL: https://issues.apache.org/jira/browse/HADOOP-17664 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 3.3.0, 3.2.2 >Reporter: Jinpeng Chi >Assignee: Jinpeng Chi >Priority: Minor > Labels: pull-request-available > Fix For: asf-site > > Time Spent: 40m > Remaining Estimate: 0h > > Web site release changelog url 404 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17664) Fix release change log url error
[ https://issues.apache.org/jira/browse/HADOOP-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17664: --- Summary: Fix release change log url error (was: Web site release 3.2.2 changelog 404) > Fix release change log url error > > > Key: HADOOP-17664 > URL: https://issues.apache.org/jira/browse/HADOOP-17664 > Project: Hadoop Common > Issue Type: Bug > Components: documentation >Affects Versions: 3.3.0, 3.2.2 >Reporter: Jinpeng Chi >Assignee: Jinpeng Chi >Priority: Minor > Labels: pull-request-available > Fix For: asf-site > > Time Spent: 40m > Remaining Estimate: 0h > > Web site release changelog url 404 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17660) Update dependency-check-maven version
[ https://issues.apache.org/jira/browse/HADOOP-17660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17660. Fix Version/s: thirdparty-1.1.0 Hadoop Flags: Reviewed Resolution: Fixed Merged the PR. > Update dependency-check-maven version > - > > Key: HADOOP-17660 > URL: https://issues.apache.org/jira/browse/HADOOP-17660 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: thirdparty-1.1.0 >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: thirdparty-1.1.0 > > > The version of org.owasp:dependency-check-maven we use (1.4.3) is too old. > The command (mvn dependency-check:aggregate) doesn't even run. Update to the > latest version. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17648) Update guava to 30.1.1-jre
[ https://issues.apache.org/jira/browse/HADOOP-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17648. Fix Version/s: thirdparty-1.1.0 Hadoop Flags: Reviewed Assignee: Wei-Chiu Chuang Resolution: Fixed > Update guava to 30.1.1-jre > -- > > Key: HADOOP-17648 > URL: https://issues.apache.org/jira/browse/HADOOP-17648 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: thirdparty-1.1.0 > > > The latest guava version is 30.1.1-jre. Let's bump the version. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17648) Update guava to 30.1.1-jre
[ https://issues.apache.org/jira/browse/HADOOP-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331731#comment-17331731 ] Akira Ajisaka commented on HADOOP-17648: Merged the PR. Closing. > Update guava to 30.1.1-jre > -- > > Key: HADOOP-17648 > URL: https://issues.apache.org/jira/browse/HADOOP-17648 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: thirdparty-1.1.0 > > > The latest guava version is 30.1.1-jre. Let's bump the version. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17667) Add precommit check for Hadoop Thirdparty repository
[ https://issues.apache.org/jira/browse/HADOOP-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331992#comment-17331992 ] Akira Ajisaka commented on HADOOP-17667: Maybe we can use GitHub Actions. > Add precommit check for Hadoop Thirdparty repository > > > Key: HADOOP-17667 > URL: https://issues.apache.org/jira/browse/HADOOP-17667 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Priority: Major > > Not a blocker for thirparty-1.1.0 release, but it would help a lot if we have > a precommit check for the hadoop-thirdparty. HBase thirdparty is a good > example. > > Reference: HBASE-24899 and > [https://ci-hadoop.apache.org/view/HBase/job/HBase/job/HBase-Thirdparty-PreCommit/configure] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17661) mvn versions:set fails to parse pom.xml
[
https://issues.apache.org/jira/browse/HADOOP-17661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved HADOOP-17661.
Fix Version/s: 3.1.5
Hadoop Flags: Reviewed
Resolution: Fixed
Merged PR #2956 into trunk, branch-3.3, branch-3.2, and branch-3.1.
> mvn versions:set fails to parse pom.xml
> ---
>
> Key: HADOOP-17661
> URL: https://issues.apache.org/jira/browse/HADOOP-17661
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
>Affects Versions: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>Reporter: Wei-Chiu Chuang
>Assignee: Wei-Chiu Chuang
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Run the following command on trunk
> mvn versions:set -DnewVersion=3.4.0
> {noformat}
> [ERROR] Failed to execute goal
> org.codehaus.mojo:versions-maven-plugin:2.8.1:set (default-cli) on project
> hadoop-main: Execution default-cli of goal
> org.codehaus.mojo:versions-maven-plugin:2.8.1:set failed: Error parsing
> /Users/weichiu/sandbox/hadoop/hadoop-project/pom.xml: Unexpected character
> '-' (code 45) (expected a name start character)
> [ERROR] at [row,col {unknown-source}]: [2288,12]
> {noformat}
> Someone else reported the same issue
> https://github.com/mojohaus/versions-maven-plugin/issues/429
> Maven: 3.3.9 ~ 3.8.1
> Affects trunk ~ branch-3.0. (But branch-2.10 is not affected)
> We don't use versions-maven-plugin directly, and I couldn't find out when it
> was updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17656) Upgrade JUnit to 4.13.1
[ https://issues.apache.org/jira/browse/HADOOP-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17656: --- Fix Version/s: (was: 3.3.1) (was: 3.1.1) > Upgrade JUnit to 4.13.1 > --- > > Key: HADOOP-17656 > URL: https://issues.apache.org/jira/browse/HADOOP-17656 > Project: Hadoop Common > Issue Type: Improvement > Components: build, security, test >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Major > Labels: TimeLine > > Yarn Timeline Server still using 4.11 Junit version, need to upgrade it to > 4.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17656) Upgrade JUnit to 4.13.1
[ https://issues.apache.org/jira/browse/HADOOP-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332931#comment-17332931 ] Akira Ajisaka commented on HADOOP-17656: Removed "Fix version/s". It is set by a committer when the fix is committed. > Upgrade JUnit to 4.13.1 > --- > > Key: HADOOP-17656 > URL: https://issues.apache.org/jira/browse/HADOOP-17656 > Project: Hadoop Common > Issue Type: Improvement > Components: build, security, test >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Major > Labels: TimeLine > > Yarn Timeline Server still using 4.11 Junit version, need to upgrade it to > 4.13.1 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17656) Upgrade JUnit to 4.13.1
[
https://issues.apache.org/jira/browse/HADOOP-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332933#comment-17332933
]
Akira Ajisaka commented on HADOOP-17656:
There are JUnit 4.11 javadoc dependencies in some modules like below:
{noformat}
org.apache.maven.plugins
maven-javadoc-plugin
junit
junit
4.11
{noformat}
They were added by
https://issues.apache.org/jira/browse/YARN-3901?focusedCommentId=14791367&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14791367.
I think the dependency is not required after YARN-5045 and can be removed.
> Upgrade JUnit to 4.13.1
> ---
>
> Key: HADOOP-17656
> URL: https://issues.apache.org/jira/browse/HADOOP-17656
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, security, test
>Affects Versions: 3.1.1
>Reporter: ANANDA G B
>Priority: Major
> Labels: TimeLine
>
> Yarn Timeline Server still using 4.11 Junit version, need to upgrade it to
> 4.13.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17255) JavaKeyStoreProvider fails to create a new key if the keystore is HDFS
[ https://issues.apache.org/jira/browse/HADOOP-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17255: --- Target Version/s: (was: 3.3.1, 3.4.0, 3.1.5, 2.10.2, 3.2.3) > JavaKeyStoreProvider fails to create a new key if the keystore is HDFS > -- > > Key: HADOOP-17255 > URL: https://issues.apache.org/jira/browse/HADOOP-17255 > Project: Hadoop Common > Issue Type: Bug > Components: kms >Reporter: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > The caller of JavaKeyStoreProvider#renameOrFail assumes that it throws > FileNotFoundException if the src does not exist. However, > JavaKeyStoreProvider#renameOrFail calls the old rename API. In > DistributedFileSystem, the old API returns false if the src does not exist. > That way JavaKeyStoreProvider fails to create a new key if the keystore is > HDFS. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17255) JavaKeyStoreProvider fails to create a new key if the keystore is HDFS
[ https://issues.apache.org/jira/browse/HADOOP-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332958#comment-17332958 ] Akira Ajisaka commented on HADOOP-17255: Since I'm not interested in this issue, removed the target versions. > JavaKeyStoreProvider fails to create a new key if the keystore is HDFS > -- > > Key: HADOOP-17255 > URL: https://issues.apache.org/jira/browse/HADOOP-17255 > Project: Hadoop Common > Issue Type: Bug > Components: kms >Reporter: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > The caller of JavaKeyStoreProvider#renameOrFail assumes that it throws > FileNotFoundException if the src does not exist. However, > JavaKeyStoreProvider#renameOrFail calls the old rename API. In > DistributedFileSystem, the old API returns false if the src does not exist. > That way JavaKeyStoreProvider fails to create a new key if the keystore is > HDFS. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17644) Add back the exceptions removed by HADOOP-17432 for compatibility
[ https://issues.apache.org/jira/browse/HADOOP-17644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17644: --- Labels: release-blocker (was: ) > Add back the exceptions removed by HADOOP-17432 for compatibility > - > > Key: HADOOP-17644 > URL: https://issues.apache.org/jira/browse/HADOOP-17644 > Project: Hadoop Common > Issue Type: Sub-task > Components: bulid >Reporter: Akira Ajisaka >Assignee: Quan Li >Priority: Blocker > Labels: release-blocker > > As [~ayushsaxena] commented in > https://issues.apache.org/jira/browse/HADOOP-17432?focusedCommentId=17324284&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17324284, > we need to add back the exceptions for compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16870) Use spotbugs-maven-plugin instead of findbugs-maven-plugin
[ https://issues.apache.org/jira/browse/HADOOP-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333113#comment-17333113 ] Akira Ajisaka commented on HADOOP-16870: The error occured because qbt-branch-2.10-java7 runs on Java 7 and spotbugs does not support Java 7. I disabled spotbugs in the qbt job. > Use spotbugs-maven-plugin instead of findbugs-maven-plugin > -- > > Key: HADOOP-16870 > URL: https://issues.apache.org/jira/browse/HADOOP-16870 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3 > > Attachments: HADOOP-16870.branch-2.10.001.patch > > Time Spent: 5h 50m > Remaining Estimate: 0h > > findbugs-maven-plugin is no longer maintained. Use spotbugs-maven-plugin > instead. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
Akira Ajisaka created HADOOP-17674: -- Summary: Use spotbugs-maven-plugin in hadoop-huaweicloud Key: HADOOP-17674 URL: https://issues.apache.org/jira/browse/HADOOP-17674 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Akira Ajisaka Fix For: 3.4.0 We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
[ https://issues.apache.org/jira/browse/HADOOP-17674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17674: --- Fix Version/s: (was: 3.4.0) > Use spotbugs-maven-plugin in hadoop-huaweicloud > --- > > Key: HADOOP-17674 > URL: https://issues.apache.org/jira/browse/HADOOP-17674 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Priority: Major > > We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed > hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
[ https://issues.apache.org/jira/browse/HADOOP-17674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17674: --- Target Version/s: 3.4.0 > Use spotbugs-maven-plugin in hadoop-huaweicloud > --- > > Key: HADOOP-17674 > URL: https://issues.apache.org/jira/browse/HADOOP-17674 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Priority: Major > > We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed > hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
[ https://issues.apache.org/jira/browse/HADOOP-17674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17674: -- Assignee: Akira Ajisaka > Use spotbugs-maven-plugin in hadoop-huaweicloud > --- > > Key: HADOOP-17674 > URL: https://issues.apache.org/jira/browse/HADOOP-17674 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed > hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
[ https://issues.apache.org/jira/browse/HADOOP-17674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17674: --- Status: Patch Available (was: Open) > Use spotbugs-maven-plugin in hadoop-huaweicloud > --- > > Key: HADOOP-17674 > URL: https://issues.apache.org/jira/browse/HADOOP-17674 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed > hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17674) Use spotbugs-maven-plugin in hadoop-huaweicloud
[ https://issues.apache.org/jira/browse/HADOOP-17674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17674: --- Fix Version/s: 3.4.0 Resolution: Fixed Status: Resolved (was: Patch Available) Merged the PR. > Use spotbugs-maven-plugin in hadoop-huaweicloud > --- > > Key: HADOOP-17674 > URL: https://issues.apache.org/jira/browse/HADOOP-17674 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > We replaced Findbugs with Spotbugs in HADOOP-16870. However, we missed > hadoop-huaweicloud module there. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17653) Do not use guava's Files.createTempDir()
[ https://issues.apache.org/jira/browse/HADOOP-17653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17653. Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk and branch-3.3. > Do not use guava's Files.createTempDir() > > > Key: HADOOP-17653 > URL: https://issues.apache.org/jira/browse/HADOOP-17653 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Work started] (HADOOP-17667) Add precommit check for Hadoop Thirdparty repository
[ https://issues.apache.org/jira/browse/HADOOP-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-17667 started by Akira Ajisaka. -- > Add precommit check for Hadoop Thirdparty repository > > > Key: HADOOP-17667 > URL: https://issues.apache.org/jira/browse/HADOOP-17667 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > > Not a blocker for thirparty-1.1.0 release, but it would help a lot if we have > a precommit check for the hadoop-thirdparty. HBase thirdparty is a good > example. > > Reference: HBASE-24899 and > [https://ci-hadoop.apache.org/view/HBase/job/HBase/job/HBase-Thirdparty-PreCommit/configure] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17667) Add precommit check for Hadoop Thirdparty repository
[ https://issues.apache.org/jira/browse/HADOOP-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17667: -- Assignee: Akira Ajisaka > Add precommit check for Hadoop Thirdparty repository > > > Key: HADOOP-17667 > URL: https://issues.apache.org/jira/browse/HADOOP-17667 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > > Not a blocker for thirparty-1.1.0 release, but it would help a lot if we have > a precommit check for the hadoop-thirdparty. HBase thirdparty is a good > example. > > Reference: HBASE-24899 and > [https://ci-hadoop.apache.org/view/HBase/job/HBase/job/HBase-Thirdparty-PreCommit/configure] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17667) Add precommit check for Hadoop Thirdparty repository
[ https://issues.apache.org/jira/browse/HADOOP-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17667. Fix Version/s: thirdparty-1.1.0 Resolution: Fixed Merged the PR into master. > Add precommit check for Hadoop Thirdparty repository > > > Key: HADOOP-17667 > URL: https://issues.apache.org/jira/browse/HADOOP-17667 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: thirdparty-1.1.0 > > > Not a blocker for thirparty-1.1.0 release, but it would help a lot if we have > a precommit check for the hadoop-thirdparty. HBase thirdparty is a good > example. > > Reference: HBASE-24899 and > [https://ci-hadoop.apache.org/view/HBase/job/HBase/job/HBase-Thirdparty-PreCommit/configure] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-17667) Add precommit check for Hadoop Thirdparty repository
[ https://issues.apache.org/jira/browse/HADOOP-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337902#comment-17337902 ] Akira Ajisaka edited comment on HADOOP-17667 at 5/2/21, 2:27 AM: - Merged the PR into trunk. was (Author: ajisakaa): Merged the PR into master. > Add precommit check for Hadoop Thirdparty repository > > > Key: HADOOP-17667 > URL: https://issues.apache.org/jira/browse/HADOOP-17667 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: thirdparty-1.1.0 > > > Not a blocker for thirparty-1.1.0 release, but it would help a lot if we have > a precommit check for the hadoop-thirdparty. HBase thirdparty is a good > example. > > Reference: HBASE-24899 and > [https://ci-hadoop.apache.org/view/HBase/job/HBase/job/HBase-Thirdparty-PreCommit/configure] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17676) Restrict imports from org.apache.curator.shaded
[ https://issues.apache.org/jira/browse/HADOOP-17676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17676: --- Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-3.3. > Restrict imports from org.apache.curator.shaded > --- > > Key: HADOOP-17676 > URL: https://issues.apache.org/jira/browse/HADOOP-17676 > Project: Hadoop Common > Issue Type: Task >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Once HADOOP-17653 gets in, we should ban "org.apache.curator.shaded" imports > as discussed on PR#2945. We can use enforcer-rule to restrict imports such > that if ever used, mvn build fails. > Thanks for the suggestion [~weichiu] [~aajisaka] [~ste...@apache.org] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-11616) Remove workaround for Curator's ChildReaper requiring Guava 15+
[
https://issues.apache.org/jira/browse/HADOOP-11616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-11616:
---
Fix Version/s: 3.4.0
3.3.1
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged the PR into trunk and branch-3.3.
> Remove workaround for Curator's ChildReaper requiring Guava 15+
> ---
>
> Key: HADOOP-11616
> URL: https://issues.apache.org/jira/browse/HADOOP-11616
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha1
>Reporter: Robert Kanter
>Assignee: Viraj Jasani
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> HADOOP-11612 adds a copy of Curator 2.7.1's {{ChildReaper}} and
> {{TestChildReaper}} with minor modifications to work with Guava 11.0.2. We
> should remove these classes and update any usages to point to Curator itself
> once we update Guava.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17684) Fix javac warnings introduced by JUnit 4.13.1
Akira Ajisaka created HADOOP-17684: -- Summary: Fix javac warnings introduced by JUnit 4.13.1 Key: HADOOP-17684 URL: https://issues.apache.org/jira/browse/HADOOP-17684 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Akira Ajisaka HADOOP-17602 updated JUnit to 4.13.1, and Assert.assertThat is deprecated. It can be replaced with AssertJ (Assertions.assertThat). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17685) Fix junit deprecation warnings in hadoop-common module
Akira Ajisaka created HADOOP-17685: -- Summary: Fix junit deprecation warnings in hadoop-common module Key: HADOOP-17685 URL: https://issues.apache.org/jira/browse/HADOOP-17685 Project: Hadoop Common Issue Type: Sub-task Components: test Reporter: Akira Ajisaka Assignee: Akira Ajisaka Fix HADOOP-17684 in hadoop-common module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17684) Fix javac warnings introduced by JUnit 4.13.1
[ https://issues.apache.org/jira/browse/HADOOP-17684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340140#comment-17340140 ] Akira Ajisaka commented on HADOOP-17684: Feel free to create subtasks for each module and provide some fixes. > Fix javac warnings introduced by JUnit 4.13.1 > - > > Key: HADOOP-17684 > URL: https://issues.apache.org/jira/browse/HADOOP-17684 > Project: Hadoop Common > Issue Type: Bug > Components: test >Reporter: Akira Ajisaka >Priority: Major > > HADOOP-17602 updated JUnit to 4.13.1, and Assert.assertThat is deprecated. It > can be replaced with AssertJ (Assertions.assertThat). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17685) Fix junit deprecation warnings in hadoop-common module
[ https://issues.apache.org/jira/browse/HADOOP-17685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17685: --- Status: Patch Available (was: Open) PR opened: https://github.com/apache/hadoop/pull/2983 > Fix junit deprecation warnings in hadoop-common module > -- > > Key: HADOOP-17685 > URL: https://issues.apache.org/jira/browse/HADOOP-17685 > Project: Hadoop Common > Issue Type: Sub-task > Components: test >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Fix HADOOP-17684 in hadoop-common module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17685) Fix junit deprecation warnings in hadoop-common module
[ https://issues.apache.org/jira/browse/HADOOP-17685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17685: --- Target Version/s: 3.4.0 > Fix junit deprecation warnings in hadoop-common module > -- > > Key: HADOOP-17685 > URL: https://issues.apache.org/jira/browse/HADOOP-17685 > Project: Hadoop Common > Issue Type: Sub-task > Components: test >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Fix HADOOP-17684 in hadoop-common module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17375) Fix the error of TestDynamometerInfra
[
https://issues.apache.org/jira/browse/HADOOP-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17375:
---
Fix Version/s: 3.4.0
3.3.1
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-3.3.
> Fix the error of TestDynamometerInfra
> -
>
> Key: HADOOP-17375
> URL: https://issues.apache.org/jira/browse/HADOOP-17375
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
>Reporter: Akira Ajisaka
>Assignee: Takanobu Asanuma
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/321/artifact/out/patch-unit-hadoop-tools_hadoop-dynamometer_hadoop-dynamometer-infra.txt
> {noformat}
> [INFO] Running org.apache.hadoop.tools.dynamometer.TestDynamometerInfra
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.43
> s <<< FAILURE! - in org.apache.hadoop.tools.dynamometer.TestDynamometerInfra
> [ERROR] org.apache.hadoop.tools.dynamometer.TestDynamometerInfra Time
> elapsed: 0.43 s <<< ERROR!
> java.io.FileNotFoundException:
> http://mirrors.ocf.berkeley.edu/apache/hadoop/common/hadoop-3.1.3/hadoop-3.1.3.tar.gz
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
> at org.apache.commons.io.FileUtils.copyURLToFile(FileUtils.java:1506)
> at
> org.apache.hadoop.tools.dynamometer.DynoInfraUtils.fetchHadoopTarball(DynoInfraUtils.java:151)
> at
> org.apache.hadoop.tools.dynamometer.TestDynamometerInfra.setupClass(TestDynamometerInfra.java:176)
> 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.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17036) TestFTPFileSystem failing as ftp server dir already exists
[ https://issues.apache.org/jira/browse/HADOOP-17036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17036: --- Fix Version/s: 3.3.1 Backported to branch-3.3. > TestFTPFileSystem failing as ftp server dir already exists > -- > > Key: HADOOP-17036 > URL: https://issues.apache.org/jira/browse/HADOOP-17036 > Project: Hadoop Common > Issue Type: Improvement > Components: fs, test >Affects Versions: 3.4.0 >Reporter: Steve Loughran >Assignee: Mikhail Pryakhin >Priority: Minor > Fix For: 3.3.1, 3.4.0 > > > TestFTPFileSystem failing as the test dir exists. > need to delete in setup/teardown of each test case -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17683) Update commons-io to 2.8.0
[ https://issues.apache.org/jira/browse/HADOOP-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17683: -- Assignee: Akira Ajisaka > Update commons-io to 2.8.0 > -- > > Key: HADOOP-17683 > URL: https://issues.apache.org/jira/browse/HADOOP-17683 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 > In Apache Commons IO before 2.7, When invoking the method > FileNameUtils.normalize with an improper input string, like "//../foo", or > "\\..\foo", the result would be the same value, thus possibly providing > access to files in the parent directory, but not further above (thus > "limited" path traversal), if the calling code would use the result to > construct a path value. > We don't use this API in the Hadoop code, but it's still good to update > anyway (we're on 2.5, which is 4 years old) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17683) Update commons-io to 2.8.0
[ https://issues.apache.org/jira/browse/HADOOP-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17683. Fix Version/s: 3.4.0 3.3.1 Resolution: Fixed Committed to trunk and branch-3.3. > Update commons-io to 2.8.0 > -- > > Key: HADOOP-17683 > URL: https://issues.apache.org/jira/browse/HADOOP-17683 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 20m > Remaining Estimate: 0h > > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 > In Apache Commons IO before 2.7, When invoking the method > FileNameUtils.normalize with an improper input string, like "//../foo", or > "\\..\foo", the result would be the same value, thus possibly providing > access to files in the parent directory, but not further above (thus > "limited" path traversal), if the calling code would use the result to > construct a path value. > We don't use this API in the Hadoop code, but it's still good to update > anyway (we're on 2.5, which is 4 years old) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17697) Fix license error in GitHub Action workflow files
Akira Ajisaka created HADOOP-17697: -- Summary: Fix license error in GitHub Action workflow files Key: HADOOP-17697 URL: https://issues.apache.org/jira/browse/HADOOP-17697 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Akira Ajisaka Assignee: Akira Ajisaka License header is missing in the following files: * .github/workflows/build.yml * .github/workflows/dependency_check.yml -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17697) Fix license error in GitHub Actions workflow files
[ https://issues.apache.org/jira/browse/HADOOP-17697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17697: --- Summary: Fix license error in GitHub Actions workflow files (was: Fix license error in GitHub Action workflow files) > Fix license error in GitHub Actions workflow files > -- > > Key: HADOOP-17697 > URL: https://issues.apache.org/jira/browse/HADOOP-17697 > Project: Hadoop Common > Issue Type: Bug > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Blocker > > License header is missing in the following files: > * .github/workflows/build.yml > * .github/workflows/dependency_check.yml -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17426) Upgrade to hadoop-thirdparty-1.1.0
[ https://issues.apache.org/jira/browse/HADOOP-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17426: --- Fix Version/s: 3.4.0 Target Version/s: 3.3.1, 3.4.0 > Upgrade to hadoop-thirdparty-1.1.0 > -- > > Key: HADOOP-17426 > URL: https://issues.apache.org/jira/browse/HADOOP-17426 > Project: Hadoop Common > Issue Type: Task >Affects Versions: 3.3.1, 3.4.0 >Reporter: Ayush Saxena >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > As of now we are using the snapshot version.(1.1.0-SNAPSHOT) > Make sure to change to the released version before release. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17426) Upgrade to hadoop-thirdparty-1.1.0
[ https://issues.apache.org/jira/browse/HADOOP-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17426. Fix Version/s: 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Committed to trunk and branch-3.3. > Upgrade to hadoop-thirdparty-1.1.0 > -- > > Key: HADOOP-17426 > URL: https://issues.apache.org/jira/browse/HADOOP-17426 > Project: Hadoop Common > Issue Type: Task >Affects Versions: 3.3.1, 3.4.0 >Reporter: Ayush Saxena >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > As of now we are using the snapshot version.(1.1.0-SNAPSHOT) > Make sure to change to the released version before release. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17663) Remove useless property hadoop.assemblies.version in pom file
[ https://issues.apache.org/jira/browse/HADOOP-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17663: --- Target Version/s: 3.3.1, 3.4.0 (was: 3.4.0) > Remove useless property hadoop.assemblies.version in pom file > - > > Key: HADOOP-17663 > URL: https://issues.apache.org/jira/browse/HADOOP-17663 > Project: Hadoop Common > Issue Type: Sub-task > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Trivial > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The property hadoop.assemblies.version in hadoop-project/pom.xml is not used > anywhere. > > Remove it to avoid confusions. (As a matter of fact, this property was not > updated in branch-3.3 and it remains to be 3.3.0-SNAPSHOT) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17663) Remove useless property hadoop.assemblies.version in pom file
[ https://issues.apache.org/jira/browse/HADOOP-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17663: --- Target Version/s: 3.4.0 > Remove useless property hadoop.assemblies.version in pom file > - > > Key: HADOOP-17663 > URL: https://issues.apache.org/jira/browse/HADOOP-17663 > Project: Hadoop Common > Issue Type: Sub-task > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Trivial > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The property hadoop.assemblies.version in hadoop-project/pom.xml is not used > anywhere. > > Remove it to avoid confusions. (As a matter of fact, this property was not > updated in branch-3.3 and it remains to be 3.3.0-SNAPSHOT) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17663) Remove useless property hadoop.assemblies.version in pom file
[ https://issues.apache.org/jira/browse/HADOOP-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned HADOOP-17663: -- Assignee: Akira Ajisaka > Remove useless property hadoop.assemblies.version in pom file > - > > Key: HADOOP-17663 > URL: https://issues.apache.org/jira/browse/HADOOP-17663 > Project: Hadoop Common > Issue Type: Sub-task > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Trivial > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The property hadoop.assemblies.version in hadoop-project/pom.xml is not used > anywhere. > > Remove it to avoid confusions. (As a matter of fact, this property was not > updated in branch-3.3 and it remains to be 3.3.0-SNAPSHOT) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17663) Remove useless property hadoop.assemblies.version in pom file
[ https://issues.apache.org/jira/browse/HADOOP-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17663: --- Status: Patch Available (was: Open) > Remove useless property hadoop.assemblies.version in pom file > - > > Key: HADOOP-17663 > URL: https://issues.apache.org/jira/browse/HADOOP-17663 > Project: Hadoop Common > Issue Type: Sub-task > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Trivial > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > The property hadoop.assemblies.version in hadoop-project/pom.xml is not used > anywhere. > > Remove it to avoid confusions. (As a matter of fact, this property was not > updated in branch-3.3 and it remains to be 3.3.0-SNAPSHOT) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17663) Remove useless property hadoop.assemblies.version in pom file
[ https://issues.apache.org/jira/browse/HADOOP-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17663: --- Fix Version/s: 3.4.0 3.3.1 Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-3.3, and branch-3.3.1. > Remove useless property hadoop.assemblies.version in pom file > - > > Key: HADOOP-17663 > URL: https://issues.apache.org/jira/browse/HADOOP-17663 > Project: Hadoop Common > Issue Type: Sub-task > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Trivial > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The property hadoop.assemblies.version in hadoop-project/pom.xml is not used > anywhere. > > Remove it to avoid confusions. (As a matter of fact, this property was not > updated in branch-3.3 and it remains to be 3.3.0-SNAPSHOT) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17563) Update Bouncy Castle to 1.68
[ https://issues.apache.org/jira/browse/HADOOP-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-17563: > Update Bouncy Castle to 1.68 > > > Key: HADOOP-17563 > URL: https://issues.apache.org/jira/browse/HADOOP-17563 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0, 3.2.3 > > Time Spent: 2h > Remaining Estimate: 0h > > -Bouncy Castle 1.60 has Hash Collision Vulnerability. Let's update to 1.68.- > Bouncy Castle 1.60 has the following vulnerabilities. Let's update to 1.68. > * [https://nvd.nist.gov/vuln/detail/CVE-2020-26939] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-28052] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-15522] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17563) Update Bouncy Castle to 1.68
[ https://issues.apache.org/jira/browse/HADOOP-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17563: --- Target Version/s: (was: 3.3.1) > Update Bouncy Castle to 1.68 > > > Key: HADOOP-17563 > URL: https://issues.apache.org/jira/browse/HADOOP-17563 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > -Bouncy Castle 1.60 has Hash Collision Vulnerability. Let's update to 1.68.- > Bouncy Castle 1.60 has the following vulnerabilities. Let's update to 1.68. > * [https://nvd.nist.gov/vuln/detail/CVE-2020-26939] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-28052] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-15522] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17563) Update Bouncy Castle to 1.68
[ https://issues.apache.org/jira/browse/HADOOP-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17563: --- Fix Version/s: (was: 3.2.3) (was: 3.4.0) (was: 3.3.1) Since the patch has been reverted, I've reopened and removed the fix versions. > Update Bouncy Castle to 1.68 > > > Key: HADOOP-17563 > URL: https://issues.apache.org/jira/browse/HADOOP-17563 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Takanobu Asanuma >Assignee: Takanobu Asanuma >Priority: Major > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > -Bouncy Castle 1.60 has Hash Collision Vulnerability. Let's update to 1.68.- > Bouncy Castle 1.60 has the following vulnerabilities. Let's update to 1.68. > * [https://nvd.nist.gov/vuln/detail/CVE-2020-26939] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-28052] > * [https://nvd.nist.gov/vuln/detail/CVE-2020-15522] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17544) Mark KeyProvider as Stable
[
https://issues.apache.org/jira/browse/HADOOP-17544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355645#comment-17355645
]
Akira Ajisaka commented on HADOOP-17544:
FYI: LinkedIn used the KeyProvider interface to integrate the company's
internal service.
[https://engineering.linkedin.com/blog/2021/the-exabyte-club--linkedin-s-journey-of-scaling-the-hadoop-distr]
{quote}LinkedIn has its own key management service, LiKMS, which is the only
service certified and approved for managing cryptographic keys and secrets
internally. We used pluggable interfaces such as KeyProvider supported by HDFS
to integrate LiKMS with transparent encryption at rest.
{quote}
> Mark KeyProvider as Stable
> --
>
> Key: HADOOP-17544
> URL: https://issues.apache.org/jira/browse/HADOOP-17544
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Now, o.a.h.crypto.key.KeyProvider.java is marked Public and Unstable. I think
> the class is very stable, and it should be annotated as Stable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17544) Mark KeyProvider as Stable
[ https://issues.apache.org/jira/browse/HADOOP-17544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355646#comment-17355646 ] Akira Ajisaka commented on HADOOP-17544: Hi [~shv], what do you think? > Mark KeyProvider as Stable > -- > > Key: HADOOP-17544 > URL: https://issues.apache.org/jira/browse/HADOOP-17544 > Project: Hadoop Common > Issue Type: Improvement > Components: security >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Now, o.a.h.crypto.key.KeyProvider.java is marked Public and Unstable. I think > the class is very stable, and it should be annotated as Stable. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17651) Backport to branch-3.1 HADOOP-17371, HADOOP-17621, HADOOP-17625 to update Jetty to 9.4.39
[ https://issues.apache.org/jira/browse/HADOOP-17651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-17651: > Backport to branch-3.1 HADOOP-17371, HADOOP-17621, HADOOP-17625 to update > Jetty to 9.4.39 > - > > Key: HADOOP-17651 > URL: https://issues.apache.org/jira/browse/HADOOP-17651 > Project: Hadoop Common > Issue Type: Task >Affects Versions: 3.2.3 >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17651) Backport to branch-3.1 HADOOP-17371, HADOOP-17621, HADOOP-17625 to update Jetty to 9.4.39
[ https://issues.apache.org/jira/browse/HADOOP-17651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17651. Resolution: Won't Fix branch-3.1 is EoL. Closing as won't fix. > Backport to branch-3.1 HADOOP-17371, HADOOP-17621, HADOOP-17625 to update > Jetty to 9.4.39 > - > > Key: HADOOP-17651 > URL: https://issues.apache.org/jira/browse/HADOOP-17651 > Project: Hadoop Common > Issue Type: Task >Affects Versions: 3.2.3 >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17623) Add a publish section to the .asf.yaml file
[ https://issues.apache.org/jira/browse/HADOOP-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-17623: --- Fix Version/s: asf-site > Add a publish section to the .asf.yaml file > --- > > Key: HADOOP-17623 > URL: https://issues.apache.org/jira/browse/HADOOP-17623 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: asf-site > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17550) property 'ssl.server.keystore.location' has not been set in the ssl configuration file
[ https://issues.apache.org/jira/browse/HADOOP-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17550. Resolution: Not A Problem > property 'ssl.server.keystore.location' has not been set in the ssl > configuration file > -- > > Key: HADOOP-17550 > URL: https://issues.apache.org/jira/browse/HADOOP-17550 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 2.8.5 >Reporter: hamado dene >Priority: Major > > I trying to install hadoop cluster HA , but datanode does not start properly; > I get this errror: > 2021-02-23 17:13:26,934 ERROR > org.apache.hadoop.hdfs.server.datanode.DataNode: Exception in secureMain > java.io.IOException: java.security.GeneralSecurityException: The property > 'ssl.server.keystore.location' has not been set in the ssl configuration file. > at > org.apache.hadoop.hdfs.server.datanode.web.DatanodeHttpServer.(DatanodeHttpServer.java:199) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.startInfoServer(DataNode.java:905) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1303) > at org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:481) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2609) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2497) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2544) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2729) > at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2753) > Caused by: java.security.GeneralSecurityException: The property > 'ssl.server.keystore.location' has not been set in the ssl configuration file. > at > org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:152) > at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:148) > at > org.apache.hadoop.hdfs.server.datanode.web.DatanodeHttpServer.(DatanodeHttpServer.java:197) > ... 8 more > But in my ssl-server.xml i correctly set this property: > > ssl.server.keystore.location > /data/hadoop/server.jks > Keystore to be used by clients like distcp. Must be > specified. > > > > ssl.server.keystore.password > > Optional. Default value is "". > > > > ssl.server.keystore.keypassword > x > Optional. Default value is "". > > > > ssl.server.keystore.type > jks > Optional. The keystore file format, default value is "jks". > > > Do you have any suggestion to solve this problem? > my hadoop version is: 2.8.5 > java version: 8 > SO: centos 7 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16993) Hadoop 3.1.2 download link is broken
[ https://issues.apache.org/jira/browse/HADOOP-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-16993: --- Fix Version/s: asf-site > Hadoop 3.1.2 download link is broken > > > Key: HADOOP-16993 > URL: https://issues.apache.org/jira/browse/HADOOP-16993 > Project: Hadoop Common > Issue Type: Bug > Components: website >Reporter: Arpit Agarwal >Assignee: Akira Ajisaka >Priority: Major > Fix For: asf-site > > > Remove broken Hadoop 3.1.2 download links from the website. > https://hadoop.apache.org/releases.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17097) start-build-env.sh fails in branch-3.1
[
https://issues.apache.org/jira/browse/HADOOP-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reopened HADOOP-17097:
> start-build-env.sh fails in branch-3.1
> --
>
> Key: HADOOP-17097
> URL: https://issues.apache.org/jira/browse/HADOOP-17097
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Environment: Ubuntu 20.04
>Reporter: Akira Ajisaka
>Assignee: Masatake Iwasaki
>Priority: Critical
>
> ./start-build-env.sh fails to install ember-cli
> {noformat}
> npm ERR! Linux 5.4.0-37-generic
> npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "ember-cli"
> npm ERR! node v4.2.6
> npm ERR! npm v3.5.2
> npm ERR! code EMISSINGARG
> npm ERR! typeerror Error: Missing required argument #1
> npm ERR! typeerror at andLogAndFinish
> (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
> npm ERR! typeerror at fetchPackageMetadata
> (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
> npm ERR! typeerror at resolveWithNewModule
> (/usr/share/npm/lib/install/deps.js:456:12)
> npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
> npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
> npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
> npm ERR! typeerror at addRequestedAndFinish
> (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
> npm ERR! typeerror at returnAndAddMetadata
> (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
> npm ERR! typeerror at pickVersionFromRegistryDocument
> (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
> npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
> npm ERR! typeerror This is an error with npm itself. Please report this error
> at:
> npm ERR! typeerror
> npm ERR! Please include the following file with any support request:
> npm ERR! /root/npm-debug.log
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17550) property 'ssl.server.keystore.location' has not been set in the ssl configuration file
[ https://issues.apache.org/jira/browse/HADOOP-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-17550: > property 'ssl.server.keystore.location' has not been set in the ssl > configuration file > -- > > Key: HADOOP-17550 > URL: https://issues.apache.org/jira/browse/HADOOP-17550 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Affects Versions: 2.8.5 >Reporter: hamado dene >Priority: Major > > I trying to install hadoop cluster HA , but datanode does not start properly; > I get this errror: > 2021-02-23 17:13:26,934 ERROR > org.apache.hadoop.hdfs.server.datanode.DataNode: Exception in secureMain > java.io.IOException: java.security.GeneralSecurityException: The property > 'ssl.server.keystore.location' has not been set in the ssl configuration file. > at > org.apache.hadoop.hdfs.server.datanode.web.DatanodeHttpServer.(DatanodeHttpServer.java:199) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.startInfoServer(DataNode.java:905) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1303) > at org.apache.hadoop.hdfs.server.datanode.DataNode.(DataNode.java:481) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2609) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2497) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2544) > at > org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2729) > at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2753) > Caused by: java.security.GeneralSecurityException: The property > 'ssl.server.keystore.location' has not been set in the ssl configuration file. > at > org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:152) > at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:148) > at > org.apache.hadoop.hdfs.server.datanode.web.DatanodeHttpServer.(DatanodeHttpServer.java:197) > ... 8 more > But in my ssl-server.xml i correctly set this property: > > ssl.server.keystore.location > /data/hadoop/server.jks > Keystore to be used by clients like distcp. Must be > specified. > > > > ssl.server.keystore.password > > Optional. Default value is "". > > > > ssl.server.keystore.keypassword > x > Optional. Default value is "". > > > > ssl.server.keystore.type > jks > Optional. The keystore file format, default value is "jks". > > > Do you have any suggestion to solve this problem? > my hadoop version is: 2.8.5 > java version: 8 > SO: centos 7 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17097) start-build-env.sh fails in branch-3.1
[
https://issues.apache.org/jira/browse/HADOOP-17097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved HADOOP-17097.
Resolution: Won't Fix
branch-3.1 is EoL, won't fix.
> start-build-env.sh fails in branch-3.1
> --
>
> Key: HADOOP-17097
> URL: https://issues.apache.org/jira/browse/HADOOP-17097
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Environment: Ubuntu 20.04
>Reporter: Akira Ajisaka
>Assignee: Masatake Iwasaki
>Priority: Critical
>
> ./start-build-env.sh fails to install ember-cli
> {noformat}
> npm ERR! Linux 5.4.0-37-generic
> npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "ember-cli"
> npm ERR! node v4.2.6
> npm ERR! npm v3.5.2
> npm ERR! code EMISSINGARG
> npm ERR! typeerror Error: Missing required argument #1
> npm ERR! typeerror at andLogAndFinish
> (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
> npm ERR! typeerror at fetchPackageMetadata
> (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
> npm ERR! typeerror at resolveWithNewModule
> (/usr/share/npm/lib/install/deps.js:456:12)
> npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
> npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
> npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
> npm ERR! typeerror at addRequestedAndFinish
> (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
> npm ERR! typeerror at returnAndAddMetadata
> (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
> npm ERR! typeerror at pickVersionFromRegistryDocument
> (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
> npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
> npm ERR! typeerror This is an error with npm itself. Please report this error
> at:
> npm ERR! typeerror
> npm ERR! Please include the following file with any support request:
> npm ERR! /root/npm-debug.log
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17228) Backport HADOOP-13230 listing changes for preserved directory markers to 3.1.x
[ https://issues.apache.org/jira/browse/HADOOP-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-17228: > Backport HADOOP-13230 listing changes for preserved directory markers to 3.1.x > -- > > Key: HADOOP-17228 > URL: https://issues.apache.org/jira/browse/HADOOP-17228 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 3.1.4 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Backport a small subset of HADOOP-17199 to branch-3.1 > No path capabities, declarative test syntax etc > just > -getFileStatus/list > -markers changes to bucket-info > -startup info message if option is set > -relevant test changes -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17228) Backport HADOOP-13230 listing changes for preserved directory markers to 3.1.x
[ https://issues.apache.org/jira/browse/HADOOP-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17228. Resolution: Won't Fix branch-3.1 is EOL, won't fix. > Backport HADOOP-13230 listing changes for preserved directory markers to 3.1.x > -- > > Key: HADOOP-17228 > URL: https://issues.apache.org/jira/browse/HADOOP-17228 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 3.1.4 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Backport a small subset of HADOOP-17199 to branch-3.1 > No path capabities, declarative test syntax etc > just > -getFileStatus/list > -markers changes to bucket-info > -startup info message if option is set > -relevant test changes -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14936) S3Guard: remove "experimental" from documentation
[ https://issues.apache.org/jira/browse/HADOOP-14936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HADOOP-14936: --- Fix Version/s: 3.3.0 > S3Guard: remove "experimental" from documentation > - > > Key: HADOOP-14936 > URL: https://issues.apache.org/jira/browse/HADOOP-14936 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 3.0.0-beta1 >Reporter: Aaron Fabbri >Assignee: Gabor Bota >Priority: Major > Fix For: 3.3.0 > > > I think it is time to remove the "experimental feature" designation in the > site docs for S3Guard. Discuss. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-17078) hadoop-shaded-protobuf_3_7 depends on the wrong version.
[ https://issues.apache.org/jira/browse/HADOOP-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-17078: > hadoop-shaded-protobuf_3_7 depends on the wrong version. > > > Key: HADOOP-17078 > URL: https://issues.apache.org/jira/browse/HADOOP-17078 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.0.1 >Reporter: JiangHua Zhu >Priority: Major > > When using maven to compile hadoop source code, the following exception > message appears: > [*INFO*] > ** > [*INFO*] *BUILD FAILURE* > [*INFO*] > ** > [*INFO*] Total time: 29.546 s > [*INFO*] Finished at: 2020-06-20T23:57:59+08:00 > [*INFO*] > ** > [*ERROR*] Failed to execute goal on project hadoop-common: *Could not resolve > dependencies for project org.apache.hadoop:hadoop-common:jar:3.3.0-SNAPSHOT: > Could not find artifact > org.apache.hadoop.thirdparty:hadoop-shaded-protobuf_3_7:jar:1.0.0-SNAPSHOT in > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots)* -> *[Help 1]* > [*ERROR*] > [*ERROR*] To see the full stack trace of the errors, re-run Maven with the > *-e* switch. > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging. > [*ERROR*] > [*ERROR*] For more information about the errors and possible solutions, > please read the following articles: > [*ERROR*] *[Help 1]* > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [*ERROR*] > [*ERROR*] After correcting the problems, you can resume the build with the > command > [*ERROR*] *mvn -rf :hadoop-common* -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-16988) Remove source code from branch-2
[ https://issues.apache.org/jira/browse/HADOOP-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened HADOOP-16988: > Remove source code from branch-2 > > > Key: HADOOP-16988 > URL: https://issues.apache.org/jira/browse/HADOOP-16988 > Project: Hadoop Common > Issue Type: Task >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Now, branch-2 is dead and unused. I think we can delete the entire source > code from branch-2 to avoid committing or cherry-picking to the unused branch. > Chen Liang asked ASF INFRA for help but it didn't help for us: INFRA-19581 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16988) Remove source code from branch-2
[ https://issues.apache.org/jira/browse/HADOOP-16988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-16988. Resolution: Done > Remove source code from branch-2 > > > Key: HADOOP-16988 > URL: https://issues.apache.org/jira/browse/HADOOP-16988 > Project: Hadoop Common > Issue Type: Task >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Now, branch-2 is dead and unused. I think we can delete the entire source > code from branch-2 to avoid committing or cherry-picking to the unused branch. > Chen Liang asked ASF INFRA for help but it didn't help for us: INFRA-19581 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17078) hadoop-shaded-protobuf_3_7 depends on the wrong version.
[ https://issues.apache.org/jira/browse/HADOOP-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved HADOOP-17078. Resolution: Duplicate > hadoop-shaded-protobuf_3_7 depends on the wrong version. > > > Key: HADOOP-17078 > URL: https://issues.apache.org/jira/browse/HADOOP-17078 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.0.1 >Reporter: JiangHua Zhu >Priority: Major > > When using maven to compile hadoop source code, the following exception > message appears: > [*INFO*] > ** > [*INFO*] *BUILD FAILURE* > [*INFO*] > ** > [*INFO*] Total time: 29.546 s > [*INFO*] Finished at: 2020-06-20T23:57:59+08:00 > [*INFO*] > ** > [*ERROR*] Failed to execute goal on project hadoop-common: *Could not resolve > dependencies for project org.apache.hadoop:hadoop-common:jar:3.3.0-SNAPSHOT: > Could not find artifact > org.apache.hadoop.thirdparty:hadoop-shaded-protobuf_3_7:jar:1.0.0-SNAPSHOT in > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots)* -> *[Help 1]* > [*ERROR*] > [*ERROR*] To see the full stack trace of the errors, re-run Maven with the > *-e* switch. > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug logging. > [*ERROR*] > [*ERROR*] For more information about the errors and possible solutions, > please read the following articles: > [*ERROR*] *[Help 1]* > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [*ERROR*] > [*ERROR*] After correcting the problems, you can resume the build with the > command > [*ERROR*] *mvn -rf :hadoop-common* -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17728) Deadlock in FileSystem StatisticsDataReferenceCleaner cleanUp
[
https://issues.apache.org/jira/browse/HADOOP-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-17728:
---
Fix Version/s: (was: 3.3.1)
3.3.2
Updated the fix version because this commit is not in branch-3.3.1.
FYI: The commit message is "HDFS-16033 Fix issue of the
StatisticsDataReferenceCleaner cleanUp (#3042)"
> Deadlock in FileSystem StatisticsDataReferenceCleaner cleanUp
> -
>
> Key: HADOOP-17728
> URL: https://issues.apache.org/jira/browse/HADOOP-17728
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
>Affects Versions: 3.2.1
>Reporter: yikf
>Assignee: yikf
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0, 3.2.3, 3.3.2
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> Cleaner thread will be blocked if we remove reference from ReferenceQueue
> unless the `queue.enqueue` called.
>
> As shown below, We call ReferenceQueue.remove() now while cleanUp, Call
> chain as follow：
> *StatisticsDataReferenceCleaner#queue.remove() ->
> ReferenceQueue.remove(0) -> lock.wait(0)*
> But, lock.notifyAll is called when queue.enqueue only, so Cleaner thread
> will be blocked.
>
> ThreadDump:
> {code:java}
> "Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x7f7afc088800
> nid=0x2119 in Object.wait() [0x7f7b0023]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0xc00c2f58> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:502)
> at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
> - locked <0xc00c2f58> (a java.lang.ref.Reference$Lock)
> at
> java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17354) Move Jenkinsfile outside of the root directory
Akira Ajisaka created HADOOP-17354: -- Summary: Move Jenkinsfile outside of the root directory Key: HADOOP-17354 URL: https://issues.apache.org/jira/browse/HADOOP-17354 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Akira Ajisaka The Jenkinsfile is placed under the project root directory, so when the Jenkinsfile is changed, all the Hadoop unit tests will run and it wastes a lot of time and resources. Let's move the file outside of the root directory. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
