You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2021/05/13 11:13:00 UTC

[jira] [Commented] (IGNITE-14707) The topology is not always valid after node restart depending on cluster timeout settings

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

Alexey Scherbakov commented on IGNITE-14707:
--------------------------------------------

The list of changes:
 # Implemented correct topology event handling in case nodes are restarted in quick succession.
 # Tuned SWIM protocol parameters to make topology events detection and propagation even more fast and stable.
 # Each ClusterNode now has new id field which is a temporary id changing on each restart. The topology events are bound to node id.
 # Added logging to networking using slf4j simple bridge.

> The topology is not always valid after node restart depending on cluster timeout settings
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-14707
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14707
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Alexey Scherbakov
>            Assignee: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha2
>
>
> The reporoducer is in the first branch commit
> ITNodeRestartsTest
>  



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