[
https://issues.apache.org/jira/browse/IGNITE-24345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24345:
---------------------------------------
Description:
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 they
will still need to be destroyed eventually as a result of table drop.
was:
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.
IGNITE-24345 defines that table drop should stop causing eventual storage
destruction.
> 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
> Priority: Major
> Labels: ignite-3
>
> 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 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)
