You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2025/12/29 16:19:00 UTC
[jira] [Commented] (IGNITE-24345) Defer zone destruction after drop
[ https://issues.apache.org/jira/browse/IGNITE-24345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048251#comment-18048251 ]
Roman Puchkovskiy commented on IGNITE-24345:
--------------------------------------------
The patch looks good to me
> Defer zone destruction after drop
> ---------------------------------
>
> Key: IGNITE-24345
> URL: https://issues.apache.org/jira/browse/IGNITE-24345
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Alexander Lapin
> Priority: Major
> Labels: ignite-3
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When a table is dropped, table partition storages are not destroyed immediately. Instead, this is deferred until table drop moment sinks below the LWM.
> As partitions will become per-zone (instead of per-table), we need to implement the same logic for zones. That is, zone partitions need to be destroyed only after zone drop moment sinks below the LWM.
> MV partition storages will remain per-table (at least in this Epic), so, in addition to the above, they will still need to be destroyed eventually as a result of table drop.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)