You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2021/09/03 14:17: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 ]
Mirza Aliev updated IGNITE-15398:
---------------------------------
Attachment: screenshot-1.png
> NioEventLoopGroup threads leakage
> ---------------------------------
>
> Key: IGNITE-15398
> URL: https://issues.apache.org/jira/browse/IGNITE-15398
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrey Mashenkov
> Assignee: Mirza Aliev
> Priority: Blocker
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Attachments: screenshot-1.png, screenshot-2.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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();
> 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)