[jira] [Updated] (HDFS-13382) Allocator does not initialize lotSize during hdfs mover process

2018-04-03 Thread Qingxin Wu (JIRA) 

 [ 
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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-13382) Allocator does not initialize lotSize during hdfs mover process

2018-04-02 Thread Qingxin Wu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-13382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qingxin Wu updated HDFS-13382:
--
Attachment: HDFS-13382.001.patch

> 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._ 
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Created] (HDFS-13382) Allocator does not initialize lotSize during hdfs mover process

2018-04-02 Thread Qingxin Wu (JIRA) 
Qingxin Wu created HDFS-13382:
-

 Summary: 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


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._ 

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org