ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1229) Stop ping procedure when node left event received
Date Fri, 14 Aug 2015 07:39:45 GMT

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

Denis Magda commented on IGNITE-1229:
-------------------------------------

Added a couple of tests that check a ping request interruption when a node, that is being
pinged, lefts a topology or fails.

> Stop ping procedure when node left event received 
> --------------------------------------------------
>
>                 Key: IGNITE-1229
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1229
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>            Reporter: Semen Boikov
>            Assignee: Denis Magda
>             Fix For: ignite-1.4
>
>         Attachments: ignite-1229-2.patch, ignite-1229-3.patch, ignite-1229-4.patch, ignite-1229.patch
>
>
> Node ping procedure (ServerImpl.pingNode(TcpDiscoveryNode node)) can be time consuming:
by default it 10 times tries to connect to each node's address, and now it continues to ping
even after node left/failed event is received.
> Also there is minor issue in ServerImpl.pingNode(UUID nodeId): if ping returns 'false'
then before initiating status check need to check if node is still visible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message