[
https://issues.apache.org/jira/browse/IGNITE-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829494#comment-17829494
]
Roman Puchkovskiy commented on IGNITE-21819:
--------------------------------------------
The patch looks good to me
> 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
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> 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)
