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

Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2022/08/29 10:38:00 UTC

[jira] [Updated] (IGNITE-17586) Handle lost majority of the partition raft group

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

Semyon Danilov updated IGNITE-17586:
------------------------------------
    Description: 
With https://issues.apache.org/jira/browse/IGNITE-17196 restarting in-memory nodes can cause the loss of majority.
If majority was lost but not all nodes hosting partition were shutdown, then we can't rebalance data on restart. 
We need to implement proper handling of this situation (see TableManager)

> Handle lost majority of the partition raft group
> ------------------------------------------------
>
>                 Key: IGNITE-17586
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17586
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>
> With https://issues.apache.org/jira/browse/IGNITE-17196 restarting in-memory nodes can cause the loss of majority.
> If majority was lost but not all nodes hosting partition were shutdown, then we can't rebalance data on restart. 
> We need to implement proper handling of this situation (see TableManager)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)