ignite-issues mailing list archives

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

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

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=97642 - Ignite AOP
02. http://204.14.53.152/viewQueued.html?itemId=97643 - Ignite Basic
03. http://204.14.53.152/viewQueued.html?itemId=97644 - Ignite Cache
04. http://204.14.53.152/viewQueued.html?itemId=97645 - Ignite Cache 2
05. http://204.14.53.152/viewQueued.html?itemId=97646 - Ignite Cache 3
06. http://204.14.53.152/viewQueued.html?itemId=97647 - Ignite Cache 4
07. http://204.14.53.152/viewQueued.html?itemId=97648 - Ignite Cache Expiry Policy
08. http://204.14.53.152/viewQueued.html?itemId=97649 - Ignite Cache Failover
09. http://204.14.53.152/viewQueued.html?itemId=97650 - Ignite Cache Failover Multi JVM
10. http://204.14.53.152/viewQueued.html?itemId=97651 - Ignite Cache Failover2
11. http://204.14.53.152/viewQueued.html?itemId=97652 - Ignite Cache Full API
12. http://204.14.53.152/viewQueued.html?itemId=97653 - Ignite Cache Full API Multi JVM
13. http://204.14.53.152/viewQueued.html?itemId=97654 - Ignite Cache Restarts
14. http://204.14.53.152/viewQueued.html?itemId=97655 - Ignite Cache Tx Recovery
15. http://204.14.53.152/viewQueued.html?itemId=97656 - Ignite Cloud
16. http://204.14.53.152/viewQueued.html?itemId=97657 - Ignite Compute Grid
17. http://204.14.53.152/viewQueued.html?itemId=97658 - Ignite Data Strucutures
18. http://204.14.53.152/viewQueued.html?itemId=97659 - Ignite Examples
19. http://204.14.53.152/viewQueued.html?itemId=97660 - Ignite GCE
20. http://204.14.53.152/viewQueued.html?itemId=97661 - Ignite Geospacial Indexing
21. http://204.14.53.152/viewQueued.html?itemId=97662 - Ignite H2 Indexing
22. http://204.14.53.152/viewQueued.html?itemId=97663 - Ignite Hadoop
23. http://204.14.53.152/viewQueued.html?itemId=97664 - Ignite Hibernate
24. http://204.14.53.152/viewQueued.html?itemId=97665 - Ignite IGFS
25. http://204.14.53.152/viewQueued.html?itemId=97666 - Ignite IGFS Examples
26. http://204.14.53.152/viewQueued.html?itemId=97667 - Ignite IGFS Linux and MacOS
27. http://204.14.53.152/viewQueued.html?itemId=97668 - Ignite Java Client
28. http://204.14.53.152/viewQueued.html?itemId=97669 - Ignite JDBC Driver
29. http://204.14.53.152/viewQueued.html?itemId=97670 - Ignite JTA
30. http://204.14.53.152/viewQueued.html?itemId=97671 - Ignite Logging
31. http://204.14.53.152/viewQueued.html?itemId=97672 - Ignite Queries
32. http://204.14.53.152/viewQueued.html?itemId=97673 - Ignite Scalar Examples
33. http://204.14.53.152/viewQueued.html?itemId=97674 - Ignite SPI
34. http://204.14.53.152/viewQueued.html?itemId=97675 - Ignite Spring
35. http://204.14.53.152/viewQueued.html?itemId=97676 - Ignite Start Nodes
36. http://204.14.53.152/viewQueued.html?itemId=97677 - Ignite URI Deploy SPI
37. http://204.14.53.152/viewQueued.html?itemId=97678 - Ignite Visor Console
38. http://204.14.53.152/viewQueued.html?itemId=97679 - Ignite WebSessions
39. http://204.14.53.152/viewQueued.html?itemId=97680 - 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.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