[
https://issues.apache.org/jira/browse/IGNITE-16465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539778#comment-17539778
]
Benjamin Mankowitz commented on IGNITE-16465:
---------------------------------------------
If this node really lost all persistent data, isn't the node that joins the
cluster a logically distinct node? If so, is this expected behavior? It sounds
like the real issue is how to deal with votes made by nodes that disappear.
> 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.7#820007)
