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

Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2024/03/20 14:49:00 UTC

[jira] [Updated] (IGNITE-21819) NextRowIdToBuild does not get cleared on rebalance

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

Aleksandr Polovtcev updated IGNITE-21819:
-----------------------------------------
    Description: During a rebalance, partition storages and their indexes get cleaned up. However, {{nextRowIdToBuild}}-related logic used by all index implementations does not take this into account and does not remove the current value as well as doesn't reset the cached field. In addition, Page Memory-based index storages don't reset their index meta trees and can access destroyed trees after a rebalance.

> NextRowIdToBuild does not get cleared on rebalance
> --------------------------------------------------
>
>                 Key: IGNITE-21819
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21819
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> During a rebalance, partition storages and their indexes get cleaned up. However, {{nextRowIdToBuild}}-related logic used by all index implementations does not take this into account and does not remove the current value as well as doesn't reset the cached field. In addition, Page Memory-based index storages don't reset their index meta trees and can access destroyed trees after a rebalance.



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