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 2020/02/18 10:34:00 UTC

[jira] [Updated] (IGNITE-11611) If partition consistency cannot be restored during rebalance using counters the most recent partition data should be used.

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

Alexey Scherbakov updated IGNITE-11611:
---------------------------------------
    Summary: If partition consistency cannot be restored during rebalance using counters the most recent partition data should be used.  (was: If partition consistency cannot be restored during rebalance it should be moved to LOST state.)

> If partition consistency cannot be restored during rebalance using counters the most recent partition data should be used.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11611
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11611
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Priority: Major
>             Fix For: 2.9
>
>
> This is possible if all owners are left, then returned and counters are inconsistent (no dedicated) max counter node)



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