[
https://issues.apache.org/jira/browse/IGNITE-25138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-25138:
-----------------------------------------
Description:
There exist two bugs at the moment:
# When {{IndexManager}} starts, it calls {{recoverDestructionQueue}} which
triggers index removals based on the Catalog state. However, when a table is
removed, its indexes are removed with it, and {{IndexManager}} correctly
handles this case when reacting to a Catalog event, but doesn't check if an
index was removed alongside its table, when doing the recovery.
# When {{TableManager}} starts, it should do a similar thing to the
{{IndexManager}} by recovering deletion events for removed tables. However,
such code doesn't exist.
> Table removals are not recovered on node startup
> ------------------------------------------------
>
> Key: IGNITE-25138
> URL: https://issues.apache.org/jira/browse/IGNITE-25138
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> There exist two bugs at the moment:
> # When {{IndexManager}} starts, it calls {{recoverDestructionQueue}} which
> triggers index removals based on the Catalog state. However, when a table is
> removed, its indexes are removed with it, and {{IndexManager}} correctly
> handles this case when reacting to a Catalog event, but doesn't check if an
> index was removed alongside its table, when doing the recovery.
> # When {{TableManager}} starts, it should do a similar thing to the
> {{IndexManager}} by recovering deletion events for removed tables. However,
> such code doesn't exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
