[
https://issues.apache.org/jira/browse/HDFS-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111551#comment-14111551
]
Tsz Wo Nicholas Sze commented on HDFS-6911:
-------------------------------------------
> ... , maybe a more efficient way here is to track the inode id, ...
I think it is a good idea. Let's do this improvement separately since it
cannot reuse the Balancer code.
> Archival Storage: check if a block is already scheduled in Mover
> ----------------------------------------------------------------
>
> Key: HDFS-6911
> URL: https://issues.apache.org/jira/browse/HDFS-6911
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer, namenode
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: h6911_20140823.patch, h6911_20140827.patch
>
>
> Similar to balancer, Mover should remember all blocks already scheduled to
> move (movedBlocks). Then, check it before schedule a new block move.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
