[
https://issues.apache.org/jira/browse/IGNITE-28399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Blinov updated IGNITE-28399:
---------------------------------------
Description:
TableDestructionCoordinator:
Self-contained concern with its own queue, inner class, and lifecycle
This has a clear boundary — destruction is triggered by drop events, gated by
LWM, and deferred via a priority queue.
What moves out:
* destructionEventsQueue field + DestroyTableEvent inner class
* onTableDrop(
* onLwmChanged
* destroyTableLocally
* cleanUpResourcesForDroppedTablesOnRecoveryBusy
* destroyMvStoragesForTablesNotIn
* unregisterMetricsSource
was: Self-contained concern with its own queue, inner class, and lifecycle
> Extract TableDestructionCoordinator out of TableManager
> -------------------------------------------------------
>
> Key: IGNITE-28399
> URL: https://issues.apache.org/jira/browse/IGNITE-28399
> Project: Ignite
> Issue Type: Improvement
> Reporter: Viacheslav Blinov
> Assignee: Viacheslav Blinov
> Priority: Major
> Labels: ignite-3
>
> TableDestructionCoordinator:
> Self-contained concern with its own queue, inner class, and lifecycle
> This has a clear boundary — destruction is triggered by drop events, gated by
> LWM, and deferred via a priority queue.
>
> What moves out:
> * destructionEventsQueue field + DestroyTableEvent inner class
> * onTableDrop(
> * onLwmChanged
> * destroyTableLocally
> * cleanUpResourcesForDroppedTablesOnRecoveryBusy
> * destroyMvStoragesForTablesNotIn
> * unregisterMetricsSource
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
