[
https://issues.apache.org/jira/browse/HDFS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meng gong updated HDFS-3747:
----------------------------
Attachment: TestCaseForBanlancer.java
This the TestCase which can unstablly triger this TestBug.
There is 5 nodes in this case. Two of them in Rack0 and 3 nodes in Rack1. When
one node in Rack0 have the status OverUtilized and one node in Rack1 have the
status BelowUtilized. Balancer try to move blocks from rack0 to rack1 but this
will reduce the num of racks in replication. So it will loop in the source of
Balancer.java:
while(!isTimeUp && scheduledSize>0 &&
(!srcBlockList.isEmpty() || blocksToReceive>0))
until isTimeUp is 20min but the maven will think the test failed in the 15min.
> 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
