[
https://issues.apache.org/jira/browse/HDDS-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057521#comment-18057521
]
Wei-Chiu Chuang commented on HDDS-3010:
---------------------------------------
We have this. Does it mean this is implemented?
{quote}
* `ozone.scm.pipeline.owner.container.count`: This property is described as
"Number of containers per owner per disk in a pipeline." This directly
addresses the "number of open containers per pipeline based on the number
of disks" aspect of your question.
* `ozone.scm.datanode.pipeline.limit`: The description for this property
states: "Max number of pipelines per datanode can be engaged in. Setting the
value to 0 means the pipeline limit per dn will be determined by the no of
metadata volumes reported per dn." This confirms that the system can
dynamically determine the pipeline limit per Datanode based on the number
of available disk-backed metadata volumes, which aligns with your requirement
of leveraging the number of disks.
* `ozone.scm.pipeline.per.metadata.disk`: This property indicates "Number of
pipelines to be created per raft log disk."
{quote}
> Containers per pipeline should be based on number of disks
> ----------------------------------------------------------
>
> Key: HDDS-3010
> URL: https://issues.apache.org/jira/browse/HDDS-3010
> Project: Apache Ozone
> Issue Type: New Feature
> Reporter: Bharat Viswanadham
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: teragentest
>
> We can configure the number of open containers per pipeline based on the
> number of disks on the datanodes involved in the ratis ring.
>
> The advantage of this is, we can make use of all disks on the data node when
> blocks/containers are allocated on the pipeline.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
