You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2023/10/20 19:46:00 UTC
[jira] [Commented] (HDDS-9516) Correct the default number of pipelines limit
[ https://issues.apache.org/jira/browse/HDDS-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777942#comment-17777942 ]
Ethan Rose commented on HDDS-9516:
----------------------------------
The description says "number of metadata volumes", but I don't think that is correct. Datanodes usually only have 1 metadata volume for raft logs. The config should be set to number of data volumes by default. I think making this the default is sensible, but we should check the code to make sure the correct type of volume is being used to set the default.
> Correct the default number of pipelines limit
> ---------------------------------------------
>
> Key: HDDS-9516
> URL: https://issues.apache.org/jira/browse/HDDS-9516
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode, SCM
> Reporter: Duong
> Priority: Major
> Labels: performance
>
> The config "ozone.scm.datanode.pipeline.limit" is now 2 by default, which needs to be tweaked every time a client has more than 2 volumes in their datanodes. This should be 0 by default to allow SCM to set the limit based on the number of datanode volumes.
> {code:java}
> <name>ozone.scm.datanode.pipeline.limit</name>
> <value>2</value>
> <tag>OZONE, SCM, PIPELINE</tag>
> <description>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.
> </description>
> </property> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org