[jira] [Updated] (IGNITE-19362) Deadlock while restarting with existing raft snapshot and scheduled index rebuild

["Semyon Danilov (Jira)" <ji...@apache.org>]

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

Semyon Danilov updated IGNITE-19362:
------------------------------------
    Description: Node can't restart if there's a raft snapshot of the partition and there is a need to rebuild index. This happens due to index rebuild depending on raft nodes start. All raft nodes in turn can't start because nodes that were started first block disruptors with waitForIndex call. As a workaround, we can skip waiting for snapshot on partition raft node start  (was: Node can't restart if there's a raft snapshot of the partition and there is a need to rebuild index. This happens due to index rebuild depending on raft nodes start. All raft nodes in turn can't start because nodes that were started first block disruptors with waitForIndex call.)

> Deadlock while restarting with existing raft snapshot and scheduled index rebuild
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-19362
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19362
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Semyon Danilov
>            Assignee: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Node can't restart if there's a raft snapshot of the partition and there is a need to rebuild index. This happens due to index rebuild depending on raft nodes start. All raft nodes in turn can't start because nodes that were started first block disruptors with waitForIndex call. As a workaround, we can skip waiting for snapshot on partition raft node start



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