[ https://issues.apache.org/jira/browse/HDFS-8540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587193#comment-14587193 ]
Hudson commented on HDFS-8540: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #8021 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8021/]) Move HDFS-8540 to 2.8 in CHANGES.txt. (szetszwo: rev 1b6695a4c0d76fe18d6524cc1379bc1185708c6f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > 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: Sub-task > Components: balancer & mover > Reporter: Tsz Wo Nicholas Sze > Assignee: surendra singh lilhore > Fix For: 2.8.0 > > Attachments: HDFS-8540.patch, HDFS-8540_1.patch, HDFS-8540_2.patch, > HDFS-8540_3.patch > > > 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)