jianghuazhu commented on PR #5954:
URL: https://github.com/apache/ozone/pull/5954#issuecomment-1884107285
Thanks @szetszwo and @duongkame .
In the old configuration, ozone-site.xml:
`
<property>
<name>ozone.scm.handler.count.key</name>
<value>100</value>
</property>
`
Constant configuration:
`
public static final String OZONE_SCM_HANDLER_COUNT_KEY =
"ozone.scm.handler.count.key";
public static final int OZONE_SCM_HANDLER_COUNT_DEFAULT = 100;
`
The default thread number configuration here is 100, which is only suitable
for small clusters.
In the new configuration, ozone-site.xml:
`
<property>
<name>ozone.scm.client.handler.count.key</name>
<value>100</value>
</property>
`
`
<property>
<name>ozone.scm.block.handler.count.key</name>
<value>100</value>
</property>
`
`
<property>
<name>ozone.scm.datanode.handler.count.key</name>
<value>100</value>
</property>
`
I've kept the same default value here as 'ozone.scm.handler.count.key',
which is 100.
The new configuration can better adapt to different clusters. In our online
cluster, we have reached a cluster scale of hundreds of nodes, so I proposed
this jira.
Is your idea to keep 'ozone.scm.handler.count.key' in ozone-site.xml?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
