[
https://issues.apache.org/jira/browse/HDFS-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267239#comment-14267239
]
Tsz Wo Nicholas Sze commented on HDFS-7466:
-------------------------------------------
Benoy, thanks for showing the use case.
Approach 1 sounds good. When should mover/balancer contacts the datanodes?
How about contacting a datanode when dispatching a move, i.e.
PendingMove.dispatch()? In that way, the datanode queries are run in parallel
and are executed on-demand.
> Allow different values for dfs.datanode.balance.max.concurrent.moves per
> datanode
> ---------------------------------------------------------------------------------
>
> Key: HDFS-7466
> URL: https://issues.apache.org/jira/browse/HDFS-7466
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer & mover
> Affects Versions: 2.6.0
> Reporter: Benoy Antony
> Assignee: Benoy Antony
>
> It is possible to configure different values for
> _dfs.datanode.balance.max.concurrent.moves_ per datanode. But the value will
> be used by balancer/mover which obtains the value from its own configuration.
> The correct approach will be to obtain the value from the datanode itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
