[ 
https://issues.apache.org/jira/browse/HDDS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17267830#comment-17267830
 ] 

Lokesh Jain commented on HDDS-4656:
-----------------------------------

[~maobaolong] I think it might also be good to look at pros and cons of having 
a separate service.
We might have certain advantage of having container balancer as a service in 
SCM. It can use the rack aware placement policy in SCM to provide default 
balancing feature. Further it would be easier to use and sync with 
ReplicationManager for balancing the containers. If needed the balancing 
commands can be provided as part of admin command line.

> Add a container balancer tool or service for HDDS
> -------------------------------------------------
>
>                 Key: HDDS-4656
>                 URL: https://issues.apache.org/jira/browse/HDDS-4656
>             Project: Hadoop Distributed Data Store
>          Issue Type: New Feature
>          Components: Ozone Datanode, SCM, Tools
>    Affects Versions: 1.1.0
>            Reporter: Baolong Mao
>            Assignee: Baolong Mao
>            Priority: Major
>
> When an existing Ozone cluster is nearly full, we have to add more datanodes 
> into the Ozone cluster, but there are two issue we must face.
> - When new allocate container request coming, SCM should better to choose the 
> datanodes in low usage, if not, the performance will getting pool.
> - For read request, the existing datanodes stored lots of blocks, so they are 
> responsible for serving the read request and supply the data stream service, 
> meanwhile, the new coming datanodes can help nothing.
> If we have a balancer tool just like hdfs balancer, we can move the block or 
> container from some high usage datanodes to low, I think this is one of 
> necessary tools for Ozone.
> container balancer design doc 
> https://docs.google.com/document/d/15PdYaP6aLB18ptbcOK3XWlL4Y1PLfIP-ll30KjNPZ2g/edit?usp=sharing



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to