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

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2026/02/20 13:51:00 UTC

[jira] [Resolved] (IGNITE-27844) Find a reason behind build index commands reordering

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

Ivan Bessonov resolved IGNITE-27844.
------------------------------------
    Resolution: Fixed

> Find a reason behind build index commands reordering
> ----------------------------------------------------
>
>                 Key: IGNITE-27844
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27844
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>
> It is possible to get this:
> {code:java}
> [2026-02-13T14:44:45,710][WARN ][%ibit_n_3346%JRaft-FSMCaller-Disruptor_stripe_1-0][BuildIndexCommandHandler] Build index command reordering detected [tableId=19, partitionId=5, indexId=21, finish=false] {code}
> in {{ItBuildIndexTest#testBuildIndexOnStableTopology}} if transfer leaders from primary replicas to other nodes and increase the number of rows. This should never happen, we should figure out why.



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