[jira] [Work logged] (HDFS-15672) TestBalancerWithMultipleNameNodes#testBalancingBlockpoolsWithBlockPoolPolicy fails on trunk
[
https://issues.apache.org/jira/browse/HDFS-15672?focusedWorklogId=535919=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535919
]
ASF GitHub Bot logged work on HDFS-15672:
-
Author: ASF GitHub Bot
Created on: 14/Jan/21 07:20
Start Date: 14/Jan/21 07:20
Worklog Time Spent: 10m
Work Description: aajisaka commented on pull request #2475:
URL: https://github.com/apache/hadoop/pull/2475#issuecomment-759978624
Thank you @iwasakims for your fix!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 535919)
Time Spent: 50m (was: 40m)
> TestBalancerWithMultipleNameNodes#testBalancingBlockpoolsWithBlockPoolPolicy
> fails on trunk
> ---
>
> Key: HDFS-15672
> URL: https://issues.apache.org/jira/browse/HDFS-15672
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: Ahmed Hussein
>Assignee: Masatake Iwasaki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> qbt report shows the following error:
> {code:bash}
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.testBalancingBlockpoolsWithBlockPoolPolicy
> Failing for the past 1 build (Since Failed#317 )
> Took 10 min.
> Error Message
> test timed out after 60 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 60
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.sleep(TestBalancerWithMultipleNameNodes.java:353)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.wait(TestBalancerWithMultipleNameNodes.java:159)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.runBalancer(TestBalancerWithMultipleNameNodes.java:175)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.runTest(TestBalancerWithMultipleNameNodes.java:550)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.testBalancingBlockpoolsWithBlockPoolPolicy(TestBalancerWithMultipleNameNodes.java:609)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15672) TestBalancerWithMultipleNameNodes#testBalancingBlockpoolsWithBlockPoolPolicy fails on trunk
[
https://issues.apache.org/jira/browse/HDFS-15672?focusedWorklogId=535918=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535918
]
ASF GitHub Bot logged work on HDFS-15672:
-
Author: ASF GitHub Bot
Created on: 14/Jan/21 07:19
Start Date: 14/Jan/21 07:19
Worklog Time Spent: 10m
Work Description: aajisaka merged pull request #2475:
URL: https://github.com/apache/hadoop/pull/2475
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 535918)
Time Spent: 40m (was: 0.5h)
> TestBalancerWithMultipleNameNodes#testBalancingBlockpoolsWithBlockPoolPolicy
> fails on trunk
> ---
>
> Key: HDFS-15672
> URL: https://issues.apache.org/jira/browse/HDFS-15672
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: Ahmed Hussein
>Assignee: Masatake Iwasaki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> qbt report shows the following error:
> {code:bash}
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.testBalancingBlockpoolsWithBlockPoolPolicy
> Failing for the past 1 build (Since Failed#317 )
> Took 10 min.
> Error Message
> test timed out after 60 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 60
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.sleep(TestBalancerWithMultipleNameNodes.java:353)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.wait(TestBalancerWithMultipleNameNodes.java:159)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.runBalancer(TestBalancerWithMultipleNameNodes.java:175)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.runTest(TestBalancerWithMultipleNameNodes.java:550)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithMultipleNameNodes.testBalancingBlockpoolsWithBlockPoolPolicy(TestBalancerWithMultipleNameNodes.java:609)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15717) Improve fsck logging
[ https://issues.apache.org/jira/browse/HDFS-15717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264646#comment-17264646 ] Akira Ajisaka commented on HDFS-15717: -- Create a PR for backporting to branch-2.10. https://github.com/apache/hadoop/pull/2620 > Improve fsck logging > > > Key: HDFS-15717 > URL: https://issues.apache.org/jira/browse/HDFS-15717 > Project: Hadoop HDFS > Issue Type: Improvement > Components: logging, namenode >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Fix For: 3.2.2, 3.3.1, 3.4.0, 3.1.5 > > Time Spent: 50m > Remaining Estimate: 0h > > Fsck always logs success and logs blockid checks as "/". -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-15717) Improve fsck logging
[ https://issues.apache.org/jira/browse/HDFS-15717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HDFS-15717: - Fix Version/s: 3.1.5 Backported to branch-3.1. > Improve fsck logging > > > Key: HDFS-15717 > URL: https://issues.apache.org/jira/browse/HDFS-15717 > Project: Hadoop HDFS > Issue Type: Improvement > Components: logging, namenode >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Fix For: 3.2.2, 3.3.1, 3.4.0, 3.1.5 > > Time Spent: 50m > Remaining Estimate: 0h > > Fsck always logs success and logs blockid checks as "/". -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15717) Improve fsck logging
[ https://issues.apache.org/jira/browse/HDFS-15717?focusedWorklogId=535914=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535914 ] ASF GitHub Bot logged work on HDFS-15717: - Author: ASF GitHub Bot Created on: 14/Jan/21 06:51 Start Date: 14/Jan/21 06:51 Worklog Time Spent: 10m Work Description: aajisaka opened a new pull request #2620: URL: https://github.com/apache/hadoop/pull/2620 …nd Ahmed Hussein (cherry picked from commit be35fa186cc0c5c1f90028a9383851d47791bf04) Backport for branch-2.10. * Fixed conflicts. * Removed lambda for JDK7. I don't have any JDK7 environment, so let me ask Jenkins to check. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 535914) Time Spent: 50m (was: 40m) > Improve fsck logging > > > Key: HDFS-15717 > URL: https://issues.apache.org/jira/browse/HDFS-15717 > Project: Hadoop HDFS > Issue Type: Improvement > Components: logging, namenode >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > Labels: pull-request-available > Fix For: 3.2.2, 3.3.1, 3.4.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Fsck always logs success and logs blockid checks as "/". -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-15771) Enable configurable trash can directory location
[ https://issues.apache.org/jira/browse/HDFS-15771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bianqi reassigned HDFS-15771: - Assignee: bianqi > Enable configurable trash can directory location > > > Key: HDFS-15771 > URL: https://issues.apache.org/jira/browse/HDFS-15771 > Project: Hadoop HDFS > Issue Type: Improvement > Components: fs >Reporter: bianqi >Assignee: bianqi >Priority: Major > Attachments: image-2021-01-11-20-29-48-274.png > > > Currently, after deleting files, if the trash can is turned on, the default > files will be placed in the /user/$USER/.Trash/Current/ directory. > Currently HDFS does not support customizing and specifying the trash can as > other directories. For example, the administrator wants to configure the > trash can as /trash/user/$USER/.Trash/Current/. But currently HDFS does not > support it. > Can you consider modifying the trash can to be configurable? By default, the > trash can directory is still /user/$USER/.Trash/Current/ > > !image-2021-01-11-20-29-48-274.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15771) Enable configurable trash can directory location
[ https://issues.apache.org/jira/browse/HDFS-15771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264561#comment-17264561 ] bianqi commented on HDFS-15771: --- [~LeonG] My code is confusing, I think it's up to you to submit the patch. I'm not sure what Hadoop PMC thinks about this issue。Maybe they don't agree。 > Enable configurable trash can directory location > > > Key: HDFS-15771 > URL: https://issues.apache.org/jira/browse/HDFS-15771 > Project: Hadoop HDFS > Issue Type: Improvement > Components: fs >Reporter: bianqi >Priority: Major > Attachments: image-2021-01-11-20-29-48-274.png > > > Currently, after deleting files, if the trash can is turned on, the default > files will be placed in the /user/$USER/.Trash/Current/ directory. > Currently HDFS does not support customizing and specifying the trash can as > other directories. For example, the administrator wants to configure the > trash can as /trash/user/$USER/.Trash/Current/. But currently HDFS does not > support it. > Can you consider modifying the trash can to be configurable? By default, the > trash can directory is still /user/$USER/.Trash/Current/ > > !image-2021-01-11-20-29-48-274.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Assigned] (HDFS-15771) Enable configurable trash can directory location
[ https://issues.apache.org/jira/browse/HDFS-15771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bianqi reassigned HDFS-15771: - Assignee: Leon Gao (was: bianqi) > Enable configurable trash can directory location > > > Key: HDFS-15771 > URL: https://issues.apache.org/jira/browse/HDFS-15771 > Project: Hadoop HDFS > Issue Type: Improvement > Components: fs >Reporter: bianqi >Assignee: Leon Gao >Priority: Major > Attachments: image-2021-01-11-20-29-48-274.png > > > Currently, after deleting files, if the trash can is turned on, the default > files will be placed in the /user/$USER/.Trash/Current/ directory. > Currently HDFS does not support customizing and specifying the trash can as > other directories. For example, the administrator wants to configure the > trash can as /trash/user/$USER/.Trash/Current/. But currently HDFS does not > support it. > Can you consider modifying the trash can to be configurable? By default, the > trash can directory is still /user/$USER/.Trash/Current/ > > !image-2021-01-11-20-29-48-274.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15762) TestMultipleNNPortQOP#testMultipleNNPortOverwriteDownStream fails intermittently
[
https://issues.apache.org/jira/browse/HDFS-15762?focusedWorklogId=535463=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535463
]
ASF GitHub Bot logged work on HDFS-15762:
-
Author: ASF GitHub Bot
Created on: 13/Jan/21 15:17
Start Date: 13/Jan/21 15:17
Worklog Time Spent: 10m
Work Description: touchida commented on pull request #2598:
URL: https://github.com/apache/hadoop/pull/2598#issuecomment-759515839
@amahussein @aajisaka Thanks for your careful reviews and commit!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 535463)
Time Spent: 3h 40m (was: 3.5h)
> TestMultipleNNPortQOP#testMultipleNNPortOverwriteDownStream fails
> intermittently
>
>
> Key: HDFS-15762
> URL: https://issues.apache.org/jira/browse/HDFS-15762
> Project: Hadoop HDFS
> Issue Type: Sub-task
>Reporter: Toshihiko Uchida
>Assignee: Toshihiko Uchida
>Priority: Minor
> Labels: flaky-test, pull-request-available
> Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
> Attachments: PR2585#1-TestMultipleNNPortQOP-output.txt
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> This unit test failed in https://github.com/apache/hadoop/pull/2585 due to an
> AssertionError.
> {code}
> java.lang.AssertionError: expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.hadoop.hdfs.TestMultipleNNPortQOP.testMultipleNNPortOverwriteDownStream(TestMultipleNNPortQOP.java:267)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.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)
> {code}
> The failure occurred at the following assertion.
> {code}
> doTest(fsPrivacy, PATH1);
> for (int i = 0; i < 2; i++) {
> DataNode dn = dataNodes.get(i);
> SaslDataTransferClient saslClient = dn.getSaslClient();
> String qop =
[jira] [Commented] (HDFS-15619) Metric for ordered snapshot deletion GC thread
[ https://issues.apache.org/jira/browse/HDFS-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264082#comment-17264082 ] Shashikant Banerjee commented on HDFS-15619: We can should also add metrics related to quota usage of deleted snapshots both in terms of namespace as well as disk space. > Metric for ordered snapshot deletion GC thread > -- > > Key: HDFS-15619 > URL: https://issues.apache.org/jira/browse/HDFS-15619 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs >Reporter: Nilotpal Nandi >Assignee: Nilotpal Nandi >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Following info should be captured and shown in JMX for garbage collection > thread of ordered snapshot deletion > * metric for all pending snapshots to be GCed > * Number of times GC thread ran > * Number of Snapshots already GCed > * Average time taken by each GC run > * Thread running Status > * metric for failed deletion of GC thread -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
