[
https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719821#comment-16719821
]
Sergey Chugunov commented on IGNITE-8766:
-----------------------------------------
[~agoncharuk],
Good catch!
I changed ServerImpl implementation so when the very first node starts up or
the very last node becomes coordinator, *tcp-disco-msg-worker* thread's name is
modified only once.
New TC Run is triggered.
> 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: Sergey Chugunov
> 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)
