[
https://issues.apache.org/jira/browse/IGNITE-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-18180:
-------------------------------------
Reviewer: Kirill Tkalenko
[~ibessonov] Looks good.
> Implement partition destruction for RocksDB
> -------------------------------------------
>
> Key: IGNITE-18180
> URL: https://issues.apache.org/jira/browse/IGNITE-18180
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> At the moment, the destruction of the partition does not work quite
> correctly, what are the problems:
> # On
> *org.apache.ignite.internal.storage.rocksdb.RocksDbTableStorage#destroyPartition*
> call we don't destroy indexes;
> # If the node falls after the call to destroy the partition and before
> flushing, then the partition will continue to exist, which may lead to
> negative consequences.
> Also important:
> # Write appropriate tests;
> # On the destruction of the partition, we must not give the opportunity to
> read data from the partition and indexes and close all existing cursors for
> the partition and indexes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
