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 2023/04/26 09:16:00 UTC

[jira] [Updated] (IGNITE-19363) Split start of indexes and start of partition raft group nodes

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

Semyon Danilov updated IGNITE-19363:
------------------------------------
    Description: Right now there is a cyclic dependency between raft group nodes recovery on start and start of indexes. To start indexes all raft nodes should be started. And raft nodes perform index rebuild on start. Index rebuild is a blocking operation which waits for the table to appear. That can't happen until all raft nodes started. As there's a smaller number of stripes in disruptor, blocking one disruptor block the start of another raft node, so table can't appear and index rebuild can't be finished.

> Split start of indexes and start of partition raft group nodes
> --------------------------------------------------------------
>
>                 Key: IGNITE-19363
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19363
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>
> Right now there is a cyclic dependency between raft group nodes recovery on start and start of indexes. To start indexes all raft nodes should be started. And raft nodes perform index rebuild on start. Index rebuild is a blocking operation which waits for the table to appear. That can't happen until all raft nodes started. As there's a smaller number of stripes in disruptor, blocking one disruptor block the start of another raft node, so table can't appear and index rebuild can't be finished.



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