ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8766) TcpDiscoverySpi: discovery threads naming
Date Thu, 05 Jul 2018 17:29:00 GMT

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

ASF GitHub Bot commented on IGNITE-8766:

GitHub user dkarachentsev opened a pull request:


    IGNITE-8766 - TcpDiscoverySpi: discovery threads naming


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8766

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4317
commit 8971f29cefe49b1b30bd885919dedef71811fe99
Author: dkarachentsev <dkarachentsev@...>
Date:   2018-07-05T17:25:18Z

    IGNITE-8766 - TcpDiscoverySpi: discovery threads naming


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

View raw message