You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2015/06/05 01:08:38 UTC

[jira] [Created] (HDFS-8540) Mover should exit with NO_MOVE_BLOCK if no block can be moved

Tsz Wo Nicholas Sze created HDFS-8540:
-----------------------------------------

             Summary: Mover should exit with NO_MOVE_BLOCK if no block can be moved
                 Key: HDFS-8540
                 URL: https://issues.apache.org/jira/browse/HDFS-8540
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: balancer & mover
            Reporter: Tsz Wo Nicholas Sze


When there are files not satisfying their storage policy and no move is possible, Mover exits with SUCCESS.  It should exit with NO_MOVE_BLOCK.

The bug seems in the following code.  When StorageTypeDiff is not empty and scheduleMoves4Block return false, it does not update hasRemaining.  Also, there is no indication of "No block can be moved" for the entire iteration.
{code}
//Mover.processFile(..)
        if (!diff.removeOverlap(true)) {
          if (scheduleMoves4Block(diff, lb, ecSchema)) {
            hasRemaining |= (diff.existing.size() > 1 &&
                diff.expected.size() > 1);
          }
        }
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)