[
https://issues.apache.org/jira/browse/HDFS-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266805#comment-14266805
]
Benoy Antony commented on HDFS-7466:
------------------------------------
[~szetszwo], My usecase is as follows:
We have DISK tier and ARCHIVE tier. The ARCHIVAL nodes doesn't have yarn
containers running on them. The read of the ARCHIVAL data is very less. The
major activity that happens on ARCHIVAL nodes is when someone moves the the
data between tiers. The DISK nodes have 12 drives whereas ARCHIVAL nodes have
60 drives.
We like to keep the dfs.datanode.balance.max.concurrent.moves on ARCHIVAL nodes
to around 60. The DISK nodes use the default value of 5.
> 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)
