[jira] [Commented] (HDFS-3747) balancer-Test failed because of time out
[ https://issues.apache.org/jira/browse/HDFS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911140#comment-13911140 ] Junping Du commented on HDFS-3747: -- The Balancer timeout bug has been fixed through HDFS-4261, HDFS-4376 and HDFS-5580, and I didn't see timeout appear for a long time. Let's close this bug, and we can reopen it if we repeat it in future. balancer-Test failed because of time out - Key: HDFS-3747 URL: https://issues.apache.org/jira/browse/HDFS-3747 Project: Hadoop HDFS Issue Type: Test Components: balancer Affects Versions: 2.0.0-alpha, 3.0.0 Reporter: meng gong Assignee: meng gong Labels: test Fix For: 3.0.0, 2.4.0 Attachments: TestCaseForBanlancer.java When run a given test case for Banlancer Test. In the test the banlancer thread try to move some block cross the rack but it can't find any available blocks in the source rack. Then the thread won't interrupt until the tag isTimeUp reaches 20min. But maven judges the test failed because the thread have runned for 15min. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HDFS-3747) balancer-Test failed because of time out
[ https://issues.apache.org/jira/browse/HDFS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427142#comment-13427142 ] meng gong commented on HDFS-3747: - Suresh Thank you! I'm a fresh man in Hadoop Community. Thank you for your direction. I'm writing some testCase for Hadoop-HDFS and find this by chance. This is a very uncommon case.But similiar events affect other TestCase I designed in boundary testing for HDFS. balancer-Test failed because of time out - Key: HDFS-3747 URL: https://issues.apache.org/jira/browse/HDFS-3747 Project: Hadoop HDFS Issue Type: Test Components: balancer Affects Versions: 2.1.0-alpha, 3.0.0 Reporter: meng gong Labels: test Fix For: 2.1.0-alpha, 3.0.0 Attachments: TestCaseForBanlancer.java When run a given test case for Banlancer Test. In the test the banlancer thread try to move some block cross the rack but it can't find any available blocks in the source rack. Then the thread won't interrupt until the tag isTimeUp reaches 20min. But maven judges the test failed because the thread have runned for 15min. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-3747) balancer-Test failed because of time out
[ https://issues.apache.org/jira/browse/HDFS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426785#comment-13426785 ] Suresh Srinivas commented on HDFS-3747: --- Meng, please add relevant description and logs when creating jiras. In case of this jira, please add the following details: # Add the name of the test that is failing, instead of just saying Balancer Test. # Please add the logs related to test failure. The information in you jira is insufficient to diagnose and fix the issue. balancer-Test failed because of time out - Key: HDFS-3747 URL: https://issues.apache.org/jira/browse/HDFS-3747 Project: Hadoop HDFS Issue Type: Test Components: balancer Affects Versions: 2.1.0-alpha, 3.0.0 Reporter: meng gong Labels: test Fix For: 2.1.0-alpha, 3.0.0 When run a given test case for Banlancer Test. In the test the banlancer thread try to move some block cross the rack but it can't find any available blocks in the source rack. Then the thread won't interrupt until the tag isTimeUp reaches 20min. But maven judges the test failed because the thread have runned for 15min. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
