[
https://issues.apache.org/jira/browse/IGNITE-18160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-18160:
-----------------------------------------
Description:
After a Raft Group is stopped on a node as a consequence of partition
reassignment, we need to remove the partition data and the corresponding Raft
log. This implies that for every storage a {{destroy}} method should be
implemented with the following behaviour: it should return control to the
caller as soon as possible, i.e. be asynchronous. Ideally this method should
perform some minimal actions to pose failover guarantees and not wait for the
data to be removed.
We need to check that every storage type supports this method and add
corresponding tests.
> Delete physical data after a Raft Group is stopped
> --------------------------------------------------
>
> Key: IGNITE-18160
> URL: https://issues.apache.org/jira/browse/IGNITE-18160
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> After a Raft Group is stopped on a node as a consequence of partition
> reassignment, we need to remove the partition data and the corresponding Raft
> log. This implies that for every storage a {{destroy}} method should be
> implemented with the following behaviour: it should return control to the
> caller as soon as possible, i.e. be asynchronous. Ideally this method should
> perform some minimal actions to pose failover guarantees and not wait for the
> data to be removed.
> We need to check that every storage type supports this method and add
> corresponding tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
