You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2020/11/13 12:45:00 UTC

[jira] [Updated] (IGNITE-13705) Fix middle node failed when failed next node and previous.

     [ https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Steshin updated IGNITE-13705:
--------------------------------------
    Description: 
The discovery ducktape test has detected failure of third node in the middle of 2 simulateously failed nodes. First research shows the trouble in backward connection checking: next node has checked itself:

[2020-11-13 14:50:44,463][INFO ][tcp-disco-sock-reader-[47cc6f70 10.53.125.224:35381]-#7-#79][org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi1] Connection check done [liveAddr=*/10.53.125.160:47500, previousNode=TcpDiscoveryNode [id=8331a61c-ea93-4bf5-bc8c-b24c032068d0, consistentId=tkles-pprb00188.vm.esrt.cloud.sbrf.ru, addrs=ArrayList [10.53.125.160], sockAddrs=HashSet [*/10.53.125.160:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1605268203598, loc=false, ver=2.10.0#20201113-sha1:00000000, isClient=false], addressesToCheck=[tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500], connectingNodeId=47cc6f70-9fe4-437d-b183-826f2687aac8]



  was:
The discovery ducktape test has detected failure of third node in the middle of 2 simulateously failed nodes. First research shows the trouble in backward connection checking: next node has checked itself:

[2020-11-13 14:50:44,463][INFO ][tcp-disco-sock-reader-[47cc6f70 10.53.125.224:35381]-#7-#79][org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi1] Connection check done [liveAddr=tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500, previousNode=TcpDiscoveryNode [id=8331a61c-ea93-4bf5-bc8c-b24c032068d0, consistentId=tkles-pprb00188.vm.esrt.cloud.sbrf.ru, addrs=ArrayList [10.53.125.160], sockAddrs=HashSet [tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1605268203598, loc=false, ver=2.10.0#20201113-sha1:00000000, isClient=false], addressesToCheck=[tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500], connectingNodeId=47cc6f70-9fe4-437d-b183-826f2687aac8]




> Fix middle node failed when failed next node and previous.
> ----------------------------------------------------------
>
>                 Key: IGNITE-13705
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13705
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladimir Steshin
>            Assignee: Vladimir Steshin
>            Priority: Major
>
> The discovery ducktape test has detected failure of third node in the middle of 2 simulateously failed nodes. First research shows the trouble in backward connection checking: next node has checked itself:
> [2020-11-13 14:50:44,463][INFO ][tcp-disco-sock-reader-[47cc6f70 10.53.125.224:35381]-#7-#79][org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi1] Connection check done [liveAddr=*/10.53.125.160:47500, previousNode=TcpDiscoveryNode [id=8331a61c-ea93-4bf5-bc8c-b24c032068d0, consistentId=tkles-pprb00188.vm.esrt.cloud.sbrf.ru, addrs=ArrayList [10.53.125.160], sockAddrs=HashSet [*/10.53.125.160:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1605268203598, loc=false, ver=2.10.0#20201113-sha1:00000000, isClient=false], addressesToCheck=[tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500], connectingNodeId=47cc6f70-9fe4-437d-b183-826f2687aac8]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)