[
https://issues.apache.org/jira/browse/HDFS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529610#comment-13529610
]
Junping Du commented on HDFS-4261:
----------------------------------
Yes. For each iteration, a new Balancer object is created but the parameter p
is the old one and passed to constructor of balancer every time. As p contains
Balancing policy which do accumulation of nodes' capacity, it needs to be
cleaned up in each iteration. So may be resetData() is still necessary here?
Also, it seems odd that testBalancerWithRackLocality() in Jenkins ends with
NO_MOVE_PROGRESS but run perfect in my env. Shall we address here or file a
separated JIRA to track this?
> TestBalancerWithNodeGroup times out
> -----------------------------------
>
> Key: HDFS-4261
> URL: https://issues.apache.org/jira/browse/HDFS-4261
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer
> Affects Versions: 1.0.4, 1.1.1, 2.0.2-alpha
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Junping Du
> Fix For: 3.0.0
>
> Attachments: HDFS-4261.patch, HDFS-4261-v2.patch, HDFS-4261-v3.patch,
> HDFS-4261-v4.patch, HDFS-4261-v5.patch, HDFS-4261-v6.patch
>
>
> When I manually ran TestBalancerWithNodeGroup, it always timed out in my
> machine. Looking at the Jerkins report [build
> #3573|https://builds.apache.org/job/PreCommit-HDFS-Build/3573//testReport/org.apache.hadoop.hdfs.server.balancer/],
> TestBalancerWithNodeGroup somehow was skipped so that the problem was not
> detected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
