You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ratis.apache.org by 宋子阳 <sz...@163.com> on 2022/05/24 06:10:46 UTC
Thirdparty configuration issues
Hi all,
Recently we upgraded Ratis from 2.2.0 to 2.3.0, and found the following warning:
org.apache.ratis.grpc.GrpcFactory - PERFORMANCE WARNING: useCacheForAllThreads is true that may cause Netty to create a lot garbage objects and, as a result, trigger GC.
It is recommended to disable useCacheForAllThreads by setting -Dorg.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads=false in command line.
We are wondering if we can directly modify this useCacheForAllThreads as a configuration field instead of setting the system env?
Best,
William Song
Re: Thirdparty configuration issues
Posted by Tsz Wo Sze <sz...@gmail.com>.
Filed https://issues.apache.org/jira/browse/RATIS-1586 .
Tsz-Wo
On Tue, May 24, 2022 at 4:48 PM Tsz Wo Sze <sz...@gmail.com> wrote:
> Hi William,
>
> > ... we upgraded Ratis from 2.2.0 to 2.3.0, ...
>
> We discovered this problem in
> https://issues.apache.org/jira/browse/RATIS-534 which was fixed in
> 0.4.0. So, it should not be related to the upgrade.
>
> > ... We are wondering if we can directly modify this
> useCacheForAllThreads as a configuration field instead of setting the
> system env?
>
> This is a good idea. The conf
> org.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads is a
> netty conf and the default is true. We should see if we can change the
> default to false in Ratis.
>
> Regards,
> Tsz-Wo
>
>
> On Tue, May 24, 2022 at 2:11 PM 宋子阳 <sz...@163.com> wrote:
>
>> Hi all,
>> Recently we upgraded Ratis from 2.2.0 to 2.3.0, and found the
>> following warning:
>>
>> org.apache.ratis.grpc.GrpcFactory - PERFORMANCE WARNING:
>> useCacheForAllThreads is true that may cause Netty to create a lot garbage
>> objects and, as a result, trigger GC.
>> It is recommended to disable useCacheForAllThreads by setting
>> -Dorg.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads=false
>> in command line.
>> We are wondering if we can directly modify this useCacheForAllThreads as
>> a configuration field instead of setting the system env?
>>
>> Best,
>> William Song
>
>
Re: Thirdparty configuration issues
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi William,
> ... we upgraded Ratis from 2.2.0 to 2.3.0, ...
We discovered this problem in
https://issues.apache.org/jira/browse/RATIS-534 which was fixed in 0.4.0.
So, it should not be related to the upgrade.
> ... We are wondering if we can directly modify this useCacheForAllThreads
as a configuration field instead of setting the system env?
This is a good idea. The conf
org.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads is a
netty conf and the default is true. We should see if we can change the
default to false in Ratis.
Regards,
Tsz-Wo
On Tue, May 24, 2022 at 2:11 PM 宋子阳 <sz...@163.com> wrote:
> Hi all,
> Recently we upgraded Ratis from 2.2.0 to 2.3.0, and found the
> following warning:
>
> org.apache.ratis.grpc.GrpcFactory - PERFORMANCE WARNING:
> useCacheForAllThreads is true that may cause Netty to create a lot garbage
> objects and, as a result, trigger GC.
> It is recommended to disable useCacheForAllThreads by setting
> -Dorg.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads=false
> in command line.
> We are wondering if we can directly modify this useCacheForAllThreads as a
> configuration field instead of setting the system env?
>
> Best,
> William Song