[ 
https://issues.apache.org/jira/browse/HDFS-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551484#comment-13551484
 ] 

Aaron T. Myers commented on HDFS-4261:
--------------------------------------

bq. I agree, when patches apply to earlier branches with trivial changes. 
However, when a significant rework is needed to port a patch back, I have been 
asking folks to create a separate jira, with an appropriate link between the 
jiras.

That's totally reasonable. trunk/branch-2 are so close to each other that the 
back-port is almost always clean or trivial, but you're right that branch-1 
back-ports often warrant a separate JIRA.
                
> 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-branch-1.patch, HDFS-4261-branch-1-v2.patch, 
> HDFS-4261.patch, HDFS-4261-v2.patch, HDFS-4261-v3.patch, HDFS-4261-v4.patch, 
> HDFS-4261-v5.patch, HDFS-4261-v6.patch, HDFS-4261-v7.patch, 
> HDFS-4261-v8.patch, jstack-mac-18567, jstack-win-5488, 
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup-output.txt.mac,
>  
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup-output.txt.win,
>  test-balancer-with-node-group-timeout.txt
>
>
> 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

Reply via email to