You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2021/08/31 07:30:00 UTC
[jira] [Updated] (IGNITE-15398) NioEventLoopGroup threads leakage
[ https://issues.apache.org/jira/browse/IGNITE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-15398:
------------------------------------
Summary: NioEventLoopGroup threads leakage (was: NioEventLoopGroup threads leakage.)
> NioEventLoopGroup threads leakage
> ---------------------------------
>
> Key: IGNITE-15398
> URL: https://issues.apache.org/jira/browse/IGNITE-15398
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrey Mashenkov
> Priority: Blocker
> Labels: ignite-3
>
> I've run a simple test and face OOM on 7 of 100 iterations.
> Seems, thread leakage is a reason.
> Use JVM arg `-Xmx512M` to run the test, otherwise more iterations may be required.
> {code:java}
> @RepeatedTest(100)
> public void nodeRestart100Test() throws Exception {
> List<Ignite> grid = startGrid();
> createTable(grid); // Just create a table. See AbstractSchemaChangeTest
> IgniteUtils.closeAll(Lists.reverse(grid));
> }
> {code}
> Thread dump shows a huge number of parked NioEventLoopGroup and JRaft-Request-Processor.
> Further investigation shows most of NioEventLoopGroup threads are acceptor threads created in startEndpoint() method of RestModule and ClientModule classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)