You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2018/01/24 08:50:00 UTC

[jira] [Updated] (IGNITE-7506) GridClusterStateProcessor#compatibilityMode flag never gets reset to false

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

Sergey Chugunov updated IGNITE-7506:
------------------------------------
    Affects Version/s: 2.4

> GridClusterStateProcessor#compatibilityMode flag never gets reset to false
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-7506
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7506
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Sergey Chugunov
>            Assignee: Sergey Chugunov
>            Priority: Major
>
> When Ignite node of version 2.4+ joins cluster with older versions of Ignite running it sets *compatibilityMode* flag to handle **cluster state in a special way (excluding BaselineTopology from discovery exchange process and so on).
> But when all old nodes are turned off there is no way except full cluster restart to enable setting very first **BaselineTopology.
> This should be addressed and some way to exit compatibilityMode without full cluster restart should be provided.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)