[
https://issues.apache.org/jira/browse/IGNITE-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291201#comment-16291201
]
ASF GitHub Bot commented on IGNITE-7206:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3234
IGNITE-7206 - Stop pings if current node is stopping.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7206
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3234.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3234
----
commit 3a8b191db5270b8dcc1599f40a580e4fc891d1bd
Author: dkarachentsev <[email protected]>
Date: 2017-12-14T17:12:51Z
IGNITE-7206 - Stop pings if current node is stopping.
----
> Nodes may ping each other on stop for a failureDetectionTimeout period
> ----------------------------------------------------------------------
>
> Key: IGNITE-7206
> URL: https://issues.apache.org/jira/browse/IGNITE-7206
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Fix For: 2.4
>
>
> On communication connection breakage TcpCommunicationSpi may try to
> reestablish connection and if it's failed try to ping remote node. But if
> remote node is stopping it refuses incoming ping connections.
> In case of concurrent few node stopping there possible case when nodes ping
> each other and refuse any incoming pings. This lasts for
> failureDetectionTimeout or reconenctCount that checks in
> ServerImpl.pingNode() method.
> pingNode() should check if local node is stopping and interrupt pings.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
