[
https://issues.apache.org/jira/browse/HDDS-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928362#comment-16928362
]
Li Cheng commented on HDDS-1569:
--------------------------------
I separate SCMAllocationManager to another Jira
https://issues.apache.org/jira/browse/HDDS-2116.
I think the current BackgroundCreator has a sync way to create pipeline and we
can start from there. As [~swagle] mentioned, we now don't assume many ad-hoc
pipeline creation operations, the current sync call from background shall be
able to handle this. Once we hit performance bottle neck for pipeline creation,
we can invest to have a SCMAllocationManager with self-managed thread model.
> Add ability to SCM for creating multiple pipelines with same datanode
> ---------------------------------------------------------------------
>
> Key: HDDS-1569
> URL: https://issues.apache.org/jira/browse/HDDS-1569
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: SCM
> Reporter: Siddharth Wagle
> Assignee: Li Cheng
> Priority: Major
>
> - Refactor _RatisPipelineProvider.create()_ to be able to create pipelines
> with datanodes that are not a part of sufficient pipelines
> - Define soft and hard upper bounds for pipeline membership
> - Create SCMAllocationManager that can be leveraged to get a candidate set of
> datanodes based on placement policies
> - Add the datanodes to internal datastructures
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
