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 2019/02/19 13:21:00 UTC
[jira] [Commented] (IGNITE-11348) Ping node procedure may fail when
another node leaves the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771916#comment-16771916 ]
Ignite TC Bot commented on IGNITE-11348:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3116051&buildTypeId=IgniteTests24Java8_RunAll]
> Ping node procedure may fail when another node leaves the cluster
> -----------------------------------------------------------------
>
> Key: IGNITE-11348
> URL: https://issues.apache.org/jira/browse/IGNITE-11348
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Critical
> Fix For: 2.8
>
>
> Additional pinging of node on join implemented in IGNITE-5569 may incorrectly fail leading to shutting down joining node.
> The reason for this is that if another node from the same host bound to the same discovery port as joining node has left the cluster right before joining node, socket used for pinging gets closed.
> This leads to the situation when pinging node considers joining node as "unreachable" and fails it with JOIN_IMPOSSIBLE error code.
> Workaround: simply start again node failed on join.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)