[
https://issues.apache.org/jira/browse/HDDS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264983#comment-17264983
]
Yiqun Lin commented on HDDS-4656:
---------------------------------
It's an interesting proposal for this, [~maobaolong].
{quote}
1. As your approach, improving the ReplicationManager and let
ReplicationManager handle the container replica placement during balance
container.
2. Copy or get a datanode topology from SCM, so balancer can choose the new
target as destination without break the rack policy.
{quote}
I also prefer to let container balancer as an independent program tool. This
balancer tool can be more flexible to implemented and to be used by admin users
in the future. Also an independent tool, it won't affect SCM core logic. HDFS
balancer is a very good example for this.
[~maobaolong], I go through the design doc. Container placement is one thing
we need to care, but another thing balancer rate limit is also very important.
How do we plan to do the rate limitation for container balance?
> 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]
