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

tc_commenter commented on IGNITE-1229:
--------------------------------------

There was triggered next test builds for last attached patch-file:
01. http://204.14.53.152/viewQueued.html?itemId=98110 - Ignite AOP
02. http://204.14.53.152/viewQueued.html?itemId=98111 - Ignite Basic
03. http://204.14.53.152/viewQueued.html?itemId=98112 - Ignite Cache
04. http://204.14.53.152/viewQueued.html?itemId=98113 - Ignite Cache 2
05. http://204.14.53.152/viewQueued.html?itemId=98114 - Ignite Cache 3
06. http://204.14.53.152/viewQueued.html?itemId=98115 - Ignite Cache 4
07. http://204.14.53.152/viewQueued.html?itemId=98116 - Ignite Cache Expiry 
Policy
08. http://204.14.53.152/viewQueued.html?itemId=98117 - Ignite Cache Failover
09. http://204.14.53.152/viewQueued.html?itemId=98118 - Ignite Cache Failover 
Multi JVM
10. http://204.14.53.152/viewQueued.html?itemId=98119 - Ignite Cache Failover2
11. http://204.14.53.152/viewQueued.html?itemId=98120 - Ignite Cache Full API
12. http://204.14.53.152/viewQueued.html?itemId=98121 - Ignite Cache Full API 
Multi JVM
13. http://204.14.53.152/viewQueued.html?itemId=98122 - Ignite Cache Restarts
14. http://204.14.53.152/viewQueued.html?itemId=98123 - Ignite Cache Tx Recovery
15. http://204.14.53.152/viewQueued.html?itemId=98124 - Ignite Cloud
16. http://204.14.53.152/viewQueued.html?itemId=98125 - Ignite Compute Grid
17. http://204.14.53.152/viewQueued.html?itemId=98126 - Ignite Data Strucutures
18. http://204.14.53.152/viewQueued.html?itemId=98127 - Ignite Examples
19. http://204.14.53.152/viewQueued.html?itemId=98128 - Ignite GCE
20. http://204.14.53.152/viewQueued.html?itemId=98129 - Ignite Geospacial 
Indexing
21. http://204.14.53.152/viewQueued.html?itemId=98130 - Ignite H2 Indexing
22. http://204.14.53.152/viewQueued.html?itemId=98131 - Ignite Hadoop
23. http://204.14.53.152/viewQueued.html?itemId=98132 - Ignite Hibernate
24. http://204.14.53.152/viewQueued.html?itemId=98133 - Ignite IGFS
25. http://204.14.53.152/viewQueued.html?itemId=98134 - Ignite IGFS Examples
26. http://204.14.53.152/viewQueued.html?itemId=98135 - Ignite IGFS Linux and 
MacOS
27. http://204.14.53.152/viewQueued.html?itemId=98136 - Ignite Java Client
28. http://204.14.53.152/viewQueued.html?itemId=98137 - Ignite JDBC Driver
29. http://204.14.53.152/viewQueued.html?itemId=98138 - Ignite JTA
30. http://204.14.53.152/viewQueued.html?itemId=98139 - Ignite Logging
31. http://204.14.53.152/viewQueued.html?itemId=98140 - Ignite Queries
32. http://204.14.53.152/viewQueued.html?itemId=98141 - Ignite Scalar Examples
33. http://204.14.53.152/viewQueued.html?itemId=98142 - Ignite SPI
34. http://204.14.53.152/viewQueued.html?itemId=98143 - Ignite Spring
35. http://204.14.53.152/viewQueued.html?itemId=98144 - Ignite Start Nodes
36. http://204.14.53.152/viewQueued.html?itemId=98145 - Ignite URI Deploy SPI
37. http://204.14.53.152/viewQueued.html?itemId=98146 - Ignite Visor Console
38. http://204.14.53.152/viewQueued.html?itemId=98147 - Ignite WebSessions
39. http://204.14.53.152/viewQueued.html?itemId=98148 - JCache TCK


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

Reply via email to