You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey N. Gura (Jira)" <ji...@apache.org> on 2021/09/27 09:50:00 UTC

[jira] [Updated] (IGNITE-15397) Use named thread pools

     [ https://issues.apache.org/jira/browse/IGNITE-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey N. Gura updated IGNITE-15397:
------------------------------------
    Labels: ignite-3 tech-debt  (was: ignite-3)

> Use named thread pools
> ----------------------
>
>                 Key: IGNITE-15397
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15397
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3, tech-debt
>             Fix For: 3.0.0-alpha3
>
>
> I've found numerous usage of NioEventLoopGroup() that creates threads with meaningless names like "nioEventLoopGroup-X-X".
> Debuging thread leakage is very hard when default names are used.
> Let's force thread pools with meaningful names.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)