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

Posted to issues@ignite.apache.org by "Benjamin Mankowitz (Jira)" <ji...@apache.org> on 2022/04/12 16:19:00 UTC

[jira] [Assigned] (IGNITE-16465) Joining a node, that completely lost persistent state, to the cluster

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

Benjamin Mankowitz reassigned IGNITE-16465:
-------------------------------------------

    Assignee: Benjamin Mankowitz

> Joining a node, that completely lost persistent state,  to the cluster 
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-16465
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16465
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vyacheslav Koptilin
>            Assignee: Benjamin Mankowitz
>            Priority: Major
>              Labels: ignite-3
>
> It looks like, local recovery and joining the node to the cluster can lead to a problem when the persistent state is completely lost (it makes sense for the in-memory cases and disk corruption) This node can participate in a leader election twice in the same term, and potentially, it can vote for different leaders.
> Need to propose a solution in order to avoid this issue.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)