ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11936) Avoid changing AffinityTopologyVersion on a server node join/left event from not baseline topology.
Date Fri, 20 Sep 2019 07:01:00 GMT

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

Anton Vinogradov commented on IGNITE-11936:
-------------------------------------------

[~NSAmelchev]
Seems, the goal is just to do not start the blocking PME in case node is outside the Baseline?
Node still able to be the proxy (client) and hold the Services? 
Is there any real difference between server node outside the Baseline and the Client node?


All these questions are about "Why should not we increment the topology?"


> Avoid changing AffinityTopologyVersion on a server node join/left event from not baseline
topology.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11936
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11936
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Amelchev Nikita
>            Assignee: Amelchev Nikita
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, a client join/left event does not change AffinityTopologyVersion (see IGNITE-9558).
It shouldn't be changed on a server node join/left event from not baseline topology too.



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

Mime
View raw message