[
https://issues.apache.org/jira/browse/IGNITE-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714856#comment-16714856
]
Sergey Chugunov edited comment on IGNITE-8766 at 12/10/18 3:03 PM:
-------------------------------------------------------------------
I reviewed changes one more time and merged latest master, according to TC Bot
there are no blocker tests.
We can proceed with merging this to master branch.
was (Author: sergey-chugunov):
I reviewed changes one more time and merged latest master, according to TC Bot
there are no blocker tests.
I think we could proceed with merging this to master branch.
> 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)
