[
https://issues.apache.org/jira/browse/IGNITE-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695177#comment-14695177
]
Denis Magda commented on IGNITE-1229:
-------------------------------------
The last patch contains the changes that allows us to interrupt a pinging
thread when it executes any blocking socket operation (connect, write, read).
Such threads are interrupted when a node, that is being pinged, leaves topology
or fails.
The last thing to do here is to create advanced tests that let us check all the
changes that were done while I was working on this task.
> 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.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)
