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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/09/25 10:21:00 UTC

[jira] [Updated] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming

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

Vladimir Ozerov updated IGNITE-8766:
------------------------------------
    Fix Version/s:     (was: 2.7)
                   2.8

> TcpDiscoverySpi: discovery threads naming
> -----------------------------------------
>
>                 Key: IGNITE-8766
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8766
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Sergey Chugunov
>            Assignee: Dmitry Karachentsev
>            Priority: Major
>              Labels: discovery
>             Fix For: 2.8
>
>
> Including information about next/prev nodes into names of discovery-related threads could be very helpful when investigating situations of network glitches.
> tcp-disco-sock-reader and tcp-disco-msg-worker threads must include such information in their names.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)