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

["Dmitry Karachentsev (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533963#comment-16533963 ] 

Dmitry Karachentsev edited comment on IGNITE-8766 at 7/5/18 5:52 PM:
---------------------------------------------------------------------

Added coordinator flag. If local node is coordinator, "crd" will be adder to ring message worker thread name:
{noformat}
"tcp-disco-msg-worker-[ebd1a087 127.0.0.1:47501 crd]-#2"
{noformat}


was (Author: dkarachentsev):
Added coordinator flag. If local node is coordinator "crd" will be adder to ring message worker thread name:
{noformat}
"tcp-disco-msg-worker-[ebd1a087 127.0.0.1:47501 crd]-#2"
{noformat}

> 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.7
>
>
> 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)