Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-3286

When the threshold value for balancer is 0(zero) ,unexpected output is displayed

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.23.0
    • Fix Version/s: 2.0.0-alpha, 3.0.0
    • Component/s: balancer
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Target Version/s:

      Description

      Replication factor =1
      Step 1: Start NN,DN1.write 4 GB of data
      Step 2: Start DN2
      Step 3: issue the balancer command(./hdfs balancer -threshold 0)

      The threshold parameter is a fraction in the range of (0%, 100%) with a default value of 10%
      When the above scenario is executed the Source DN and Target DN is choosen and the number of bytes to be moved from source to target DN is also calculated .

      Then the balancer is exiting with the following message "No block can be moved. Exiting..." which is not expected.

      HOST-xx-xx-xx-xx:/home/Andreina/APril10/install/hadoop/namenode/bin # ./hdfs balancer -threshold 0
      12/04/16 16:22:07 INFO balancer.Balancer: Using a threshold of 0.0
      12/04/16 16:22:07 INFO balancer.Balancer: namenodes = [hdfs://HOST-xx-xx-xx-xx:9000]
      12/04/16 16:22:07 INFO balancer.Balancer: p         = Balancer.Parameters[BalancingPolicy.Node, threshold=0.0]
      Time Stamp               Iteration#  Bytes Already Moved  Bytes Left To Move  Bytes Being Moved
      12/04/16 16:22:10 INFO net.NetworkTopology: Adding a new node: /default-rack/yy.yy.yy.yy:50176
      12/04/16 16:22:10 INFO net.NetworkTopology: Adding a new node: /default-rack/xx.xx.xx.xx:50010
      12/04/16 16:22:10 INFO balancer.Balancer: 1 over-utilized: [Source[xx.xx.xx.xx:50010, utilization=7.212458091389678]]
      12/04/16 16:22:10 INFO balancer.Balancer: 1 underutilized: [BalancerDatanode[yy.yy.yy.yy:50176, utilization=4.650670324367203E-5]]
      12/04/16 16:22:10 INFO balancer.Balancer: Need to move 1.77 GB to make the cluster balanced.
      No block can be moved. Exiting...
      Balancing took 5.142 seconds
      
      1. HDFS-3286.patch
        8 kB
        Ashish Singhi
      2. HDFS-3286.patch
        4 kB
        Ashish Singhi
      3. HDFS-3286.patch
        5 kB
        Ashish Singhi
      4. HDFS-3286-1.patch
        4 kB
        Ashish Singhi

        Activity

        Hide
        Ashish Singhi added a comment -

        When the threshold value is 0. The maxSizeToMove for overUtilizedDatanodes and UnderUtilizedDatanodes will be calculated to 0.

        if (utilization >= avgUtil + threshold
            || utilization <= avgUtil - threshold) {
           maxSizeToMove = (long) (threshold * datanode.getCapacity() / 100);
        } else {
        

        When maxSizeToMove is 0, we end up with no source datanode, hence bytesToMove will be equal to 0 and the following message is displayed.

        Show
        Ashish Singhi added a comment - When the threshold value is 0. The maxSizeToMove for overUtilizedDatanodes and UnderUtilizedDatanodes will be calculated to 0. if (utilization >= avgUtil + threshold || utilization <= avgUtil - threshold) { maxSizeToMove = ( long ) (threshold * datanode.getCapacity() / 100); } else { When maxSizeToMove is 0, we end up with no source datanode, hence bytesToMove will be equal to 0 and the following message is displayed.
        Hide
        Uma Maheswara Rao G added a comment -

        To fix this with 0 threshold value:
        0 threshold value may not work all the times because, cluster may not have the space to balance exactly equal spaces in DNs right?

        Show
        Uma Maheswara Rao G added a comment - To fix this with 0 threshold value: 0 threshold value may not work all the times because, cluster may not have the space to balance exactly equal spaces in DNs right?
        Hide
        Ashish Singhi added a comment -

        @Uma: Yes you are right.
        I tried this by the following code modification,

        -      if (utilization >= avgUtil+threshold
        -          || utilization <= avgUtil-threshold) { 
        -        maxSizeToMove = (long)(threshold*datanode.getCapacity()/100);
        +      if (utilization >= avgUtil + threshold
        +          || utilization <= avgUtil - threshold) {
        +        if (threshold != 0){
        +          maxSizeToMove = (long) (threshold * datanode.getCapacity() / 100);
        +        } else {
        +          maxSizeToMove = (long) (datanode.getCapacity() / 100);
        +        }
               } else {
        

        Is this modification of code, ok ?
        But with 0 threshold, balancer keeps iterating because it is very difficult to produce a threshold of 0% between the datanodes.

        I wrote a test case, cluster with 1DN then filled it 30% and then starting one more say DN2. This will take very large to get terminate.
        One possible way would be to have a cluster with 1DN fill it 30% and then starting one more say DN2 with the same usage as DN1. Then it will terminate within very less time with ReturnStatus.SUCCESS. Is it ok to have a test case like that ?

        Show
        Ashish Singhi added a comment - @Uma: Yes you are right. I tried this by the following code modification, - if (utilization >= avgUtil+threshold - || utilization <= avgUtil-threshold) { - maxSizeToMove = ( long )(threshold*datanode.getCapacity()/100); + if (utilization >= avgUtil + threshold + || utilization <= avgUtil - threshold) { + if (threshold != 0){ + maxSizeToMove = ( long ) (threshold * datanode.getCapacity() / 100); + } else { + maxSizeToMove = ( long ) (datanode.getCapacity() / 100); + } } else { Is this modification of code, ok ? But with 0 threshold, balancer keeps iterating because it is very difficult to produce a threshold of 0% between the datanodes. I wrote a test case, cluster with 1DN then filled it 30% and then starting one more say DN2. This will take very large to get terminate. One possible way would be to have a cluster with 1DN fill it 30% and then starting one more say DN2 with the same usage as DN1. Then it will terminate within very less time with ReturnStatus.SUCCESS. Is it ok to have a test case like that ?
        Hide
        Tsz Wo Nicholas Sze added a comment -

        It does make sense to set threshold to 0 since it won't work in many case as Uma mentioned. How about throw an IllegalArgumentException when threshold < 1?

        Show
        Tsz Wo Nicholas Sze added a comment - It does make sense to set threshold to 0 since it won't work in many case as Uma mentioned. How about throw an IllegalArgumentException when threshold < 1?
        Hide
        Uma Maheswara Rao G added a comment -

        How about throw an IllegalArgumentException when threshold < 1?

        Make sense to me. +1

        @Ashish, Could you please update the patch as per this suggestion?

        Show
        Uma Maheswara Rao G added a comment - How about throw an IllegalArgumentException when threshold < 1? Make sense to me. +1 @Ashish, Could you please update the patch as per this suggestion?
        Hide
        Ashish Singhi added a comment -

        Uploaded the patch based on the above comments.
        Uma/Nicholas, can u please review the patch.

        Show
        Ashish Singhi added a comment - Uploaded the patch based on the above comments. Uma/Nicholas, can u please review the patch.
        Hide
        Uma Maheswara Rao G added a comment -

        Ashish, patch looks good. Some comments.

        1) doTest javadoc may need to update with parameters?

        2) 'If null Balancer will take the default values.' — may be typo here?

        3) Since the CLI is static class, we can access directly parse api. Why can't we add the tests directly to it. May be with all boundary values. As a unit test, that should be sufficient for this change and also will ensure all boundary conditions satisfied. So, we need not start cluster, balancer right.

        Show
        Uma Maheswara Rao G added a comment - Ashish, patch looks good. Some comments. 1) doTest javadoc may need to update with parameters? 2) 'If null Balancer will take the default values.' — may be typo here? 3) Since the CLI is static class, we can access directly parse api. Why can't we add the tests directly to it. May be with all boundary values. As a unit test, that should be sufficient for this change and also will ensure all boundary conditions satisfied. So, we need not start cluster, balancer right.
        Hide
        Uma Maheswara Rao G added a comment -

        @Nicholas, do we need to mark this as incompatible change? As we are throwing IllegalArgumentException instead of NumberFormatException now.

        Show
        Uma Maheswara Rao G added a comment - @Nicholas, do we need to mark this as incompatible change? As we are throwing IllegalArgumentException instead of NumberFormatException now.
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12523929/HDFS-3286.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in .

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2318//testReport/
        Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2318//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12523929/HDFS-3286.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2318//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2318//console This message is automatically generated.
        Hide
        Ashish Singhi added a comment -

        Thanks Uma for reviewing it.
        Will upload a patch addressing your comments in some time.

        Show
        Ashish Singhi added a comment - Thanks Uma for reviewing it. Will upload a patch addressing your comments in some time.
        Hide
        Ashish Singhi added a comment -

        @Uma: Can u pls review it once again.

        Show
        Ashish Singhi added a comment - @Uma: Can u pls review it once again.
        Hide
        Ashish Singhi added a comment -

        Marking it as Incompatible change. As now we are throwing IllegalArgumentException instead of NumberFormatException.

        Show
        Ashish Singhi added a comment - Marking it as Incompatible change. As now we are throwing IllegalArgumentException instead of NumberFormatException.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524442/HDFS-3286.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed these unit tests:
        org.apache.hadoop.fs.TestUrlStreamHandler

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2333//testReport/
        Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2333//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12524442/HDFS-3286.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.fs.TestUrlStreamHandler +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2333//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2333//console This message is automatically generated.
        Hide
        Ashish Singhi added a comment -
        -1 core tests. The patch failed these unit tests:
        org.apache.hadoop.fs.TestUrlStreamHandler
        

        Not related to this fix.

        Show
        Ashish Singhi added a comment - -1 core tests. The patch failed these unit tests: org.apache.hadoop.fs.TestUrlStreamHandler Not related to this fix.
        Hide
        Uma Maheswara Rao G added a comment -

        Hi Ashish, Patch looks pretty good. One comment:

        	  try {
        +		  Balancer.Cli.parse(parameters);
        +		  fail(reason);
        +	  }
        +	  catch (IllegalArgumentException e) {
        +		  assertEquals("Number out of range: threshold = 0.0", e.getMessage());
        +	  }
        +	  parameters = new String[]{"-threshold", "101"};
        +	  try {
        +		  Balancer.Cli.parse(parameters);
        +		  fail(reason);
        +	  }
        

        Patch contains tabs, could you please format propertly.

        Show
        Uma Maheswara Rao G added a comment - Hi Ashish, Patch looks pretty good. One comment: try { + Balancer.Cli.parse(parameters); + fail(reason); + } + catch (IllegalArgumentException e) { + assertEquals( " Number out of range: threshold = 0.0" , e.getMessage()); + } + parameters = new String []{ "-threshold" , "101" }; + try { + Balancer.Cli.parse(parameters); + fail(reason); + } Patch contains tabs, could you please format propertly.
        Hide
        Aaron T. Myers added a comment -

        Minor nit: Please also put catch clauses on the same line as the closing brace of the try block.

        Show
        Aaron T. Myers added a comment - Minor nit: Please also put catch clauses on the same line as the closing brace of the try block.
        Hide
        Ashish Singhi added a comment -

        Thanks Uma and Aaron for taking a look at the patch.
        Uploaded a patch addressing all your comments.

        Show
        Ashish Singhi added a comment - Thanks Uma and Aaron for taking a look at the patch. Uploaded a patch addressing all your comments.
        Hide
        Ashish Singhi added a comment -

        Correct patch HDFS-3286-1

        Show
        Ashish Singhi added a comment - Correct patch HDFS-3286 -1
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524968/HDFS-3286-1.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in .

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2349//testReport/
        Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2349//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12524968/HDFS-3286-1.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2349//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2349//console This message is automatically generated.
        Hide
        Uma Maheswara Rao G added a comment -

        +1, looks good.

        Show
        Uma Maheswara Rao G added a comment - +1, looks good.
        Hide
        Uma Maheswara Rao G added a comment -

        I have just committed to trunk and branch-2. Thanks Ashish.

        Show
        Uma Maheswara Rao G added a comment - I have just committed to trunk and branch-2. Thanks Ashish.
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Common-trunk-Commit #2162 (See https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2162/)
        HDFS-3286. When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531)

        Result = SUCCESS
        umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531
        Files :

        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java
        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Show
        Hudson added a comment - Integrated in Hadoop-Common-trunk-Commit #2162 (See https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2162/ ) HDFS-3286 . When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531) Result = SUCCESS umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531 Files : /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk-Commit #2236 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2236/)
        HDFS-3286. When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531)

        Result = SUCCESS
        umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531
        Files :

        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java
        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk-Commit #2236 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2236/ ) HDFS-3286 . When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531) Result = SUCCESS umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531 Files : /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-trunk-Commit #2179 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2179/)
        HDFS-3286. When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531)

        Result = ABORTED
        umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531
        Files :

        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java
        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk-Commit #2179 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2179/ ) HDFS-3286 . When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531) Result = ABORTED umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531 Files : /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk #1031 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1031/)
        HDFS-3286. When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531)

        Result = FAILURE
        umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531
        Files :

        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java
        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #1031 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1031/ ) HDFS-3286 . When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531) Result = FAILURE umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531 Files : /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-trunk #1066 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1066/)
        HDFS-3286. When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531)

        Result = FAILURE
        umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531
        Files :

        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java
        • /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #1066 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1066/ ) HDFS-3286 . When the threshold value for balancer is zero, unexpected output is displayed. Contributed by Ashish Singhi. (Revision 1332531) Result = FAILURE umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332531 Files : /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/balancer/Balancer.java /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/balancer/TestBalancer.java

          People

          • Assignee:
            Ashish Singhi
            Reporter:
            J.Andreina
          • Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development