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/08/16 12:21:00 UTC

[jira] [Updated] (IGNITE-15315) Possible owners desync when a node is restarted during rebalancing with enabled persistence

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

Alexey Scherbakov updated IGNITE-15315:
---------------------------------------
    Summary: Possible owners desync when a node is restarted during rebalancing with enabled persistence  (was: Possible owners desync when a node is restarted during rebalancing using persistence)

> Possible owners desync when a node is restarted during rebalancing with enabled persistence
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-15315
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15315
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.10
>            Reporter: Alexey Scherbakov
>            Assignee: Alexey Scherbakov
>            Priority: Major
>             Fix For: 2.12
>
>
> If a node is restarted having MOVING partitions, it is possible the partition clearing version compartion logic on next rebalancing will fail due to outdated org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition#clearVer on joining node.
> The fix is to always update partition clear version when a partition is marked for rebalancing.
> The bug is only applicable to persistent mode.



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