You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2021/11/08 13:02:00 UTC
[jira] [Resolved] (RATIS-1421) make client NioEventLoopGroup size
configurable.
[ https://issues.apache.org/jira/browse/RATIS-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze resolved RATIS-1421.
-------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
I have merged the pull request. Thanks, [~micahzhao]!
> make client NioEventLoopGroup size configurable.
> ------------------------------------------------
>
> Key: RATIS-1421
> URL: https://issues.apache.org/jira/browse/RATIS-1421
> Project: Ratis
> Issue Type: Sub-task
> Components: Netty, Streaming
> Reporter: mingchao zhao
> Assignee: mingchao zhao
> Priority: Major
> Fix For: 2.3.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This used to fix HDDS-5915.
> They used S3 GateWay to test streaming, writing files over and over again.
> Too many open files appear when an OzoneClient(S3 GateWay) uses Streaming Write for a long time.
> Currently the default value is NettyRuntime.availableProcessors() * 2, and decreasing this value can avoid this problem. So we need to make it configurable to be more general.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)