[
https://issues.apache.org/jira/browse/HDFS-13382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qingxin Wu updated HDFS-13382:
------------------------------
Description:
Currently, when we execute
{code:java}
hdfs mover -p /some/path
{code}
the moverThreadAllocator in org.apache.hadoop.hdfs.server.balancer.Dispatcher
does not initialize lotSize according to _dfs.mover.moverThreads and
dfs.datanode.balance.max.concurrent.moves._ So, when we invoke
moverThreadAllocator.allocate() method, it will always return 1.
was:
Currently, when we execute
{code:java}
hdfs mover -p /some/path
{code}
the moverThreadAllocator in org.apache.hadoop.hdfs.server.balancer.Dispatcher
does not initialize lotSize according to _dfs.mover.moverThreads and
dfs.datanode.balance.max.concurrent.moves._
> Allocator does not initialize lotSize during hdfs mover process
> ---------------------------------------------------------------
>
> Key: HDFS-13382
> URL: https://issues.apache.org/jira/browse/HDFS-13382
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover
> Affects Versions: 2.7.5
> Reporter: Qingxin Wu
> Priority: Major
> Attachments: HDFS-13382.001.patch
>
>
> Currently, when we execute
> {code:java}
> hdfs mover -p /some/path
> {code}
> the moverThreadAllocator in org.apache.hadoop.hdfs.server.balancer.Dispatcher
> does not initialize lotSize according to _dfs.mover.moverThreads and
> dfs.datanode.balance.max.concurrent.moves._ So, when we invoke
> moverThreadAllocator.allocate() method, it will always return 1.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
