[
https://issues.apache.org/jira/browse/IGNITE-21750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827453#comment-17827453
]
Roman Puchkovskiy commented on IGNITE-21750:
--------------------------------------------
Thanks!
> Throw a special exception when trying to read from/write to a destroyed
> IndexStorage
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-21750
> URL: https://issues.apache.org/jira/browse/IGNITE-21750
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Also:
> # DESTROYING state is to be renamed to DESTROYED
> # DESTROYED also becomes a terminal state (like CLOSED), so after a
> destruction completes the state does not move to CLOSED
> # After a storage (partition or index) was switched to any of
> CLOSED/DESTROYED states, it should not allow normal operation (probably, its
> busy lock must be blocked forever)
> # RocksDB-based index storages need to be switched to the DESTROYED state
> when destroyIndex(int) is called on MvTableStorage
--
This message was sent by Atlassian Jira
(v8.20.10#820010)