[
https://issues.apache.org/jira/browse/HDDS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261139#comment-17261139
]
Marton Elek commented on HDDS-4656:
-----------------------------------
Thanks to open this issue [~maobaolong]. I agree, these are important goals.
Some comments:
> When new allocate container request coming, SCM should better to choose the
> datanodes in low usage, if not, the performance will getting pool.
It seems to be an improved placement policy, not a separated service, right?
> 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.
It's a good question. There were some thoughts earlier about improving the
ReplicationManager (closed clontainer replication) to handle smarter strategies
and initiate container moves (re-replication + delete) just for better
placement. But Nanda may have better memories. (Not the only way to do it, just
sharing some earlier thoughts)
> Add a container balancer tool or service for SCM
> ------------------------------------------------
>
> Key: HDDS-4656
> URL: https://issues.apache.org/jira/browse/HDDS-4656
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
