[
https://issues.apache.org/jira/browse/HDDS-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duong updated HDDS-9516:
------------------------
Description:
The config "ozone.scm.datanode.pipeline.limit" is now 2 by default, which needs
to be tweaked everytime a customer have 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}
was:
The config "ozone.scm.datanode.pipeline.limit" is now 2 by default, which needs
to be tweaked every time a customer have 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}
> 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 everytime a customer have 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: [email protected]
For additional commands, e-mail: [email protected]
