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

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2018/12/10 15:02:00 UTC

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

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

Ignite TC Bot commented on IGNITE-8766:
---------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2509249&amp;buildTypeId=IgniteTests24Java8_RunAll]

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