[
https://issues.apache.org/jira/browse/HDFS-8540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584811#comment-14584811
]
Tsz Wo Nicholas Sze commented on HDFS-8540:
-------------------------------------------
You are right about getExitStatus(). Good point! Let's return SUCCESS first
for better readability. The javadoc I posted previously also need to be fixed.
See below.
{code}
/**
* @return SUCCESS if all moves are success and there is no remaining move.
* Return NO_MOVE_BLOCK if there are moves available but all the moves
* cannot be scheduled. Otherwise, return IN_PROGRESS since there must
* be some remaining moves.
*/
ExitStatus getExitStatus() {
return !isHasRemaining()? ExitStatus.SUCCESS
: isNoBlockMoved()? ExitStatus.NO_MOVE_BLOCK: ExitStatus.IN_PROGRESS;
}
{code}
Let's ignore the check style warnings.
> 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
> Attachments: HDFS-8540.patch, HDFS-8540_1.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)
