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

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/22 05:53:00 UTC

[jira] [Updated] (IGNITE-13054) Prevent nodes with stale data joining the active topology.

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

Aleksey Plekhanov updated IGNITE-13054:
---------------------------------------
    Fix Version/s:     (was: 2.9)
                   2.10

> Prevent nodes with stale data joining the active topology.
> ----------------------------------------------------------
>
>                 Key: IGNITE-13054
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13054
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Scherbakov
>            Priority: Major
>             Fix For: 2.10
>
>
> After IGNITE-13003 LOST state is preserved then nodes with lost data are retuned to topology after failure.
> If resetting is performed on lesser topology, it's possible to get into sutiation where a node with most recent data is returned to active topology where some key already could be modified.
> This should not be allowed because brings conflicting data into grid. 



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