You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2024/03/15 07:06:00 UTC

[jira] [Commented] (IGNITE-21750) Throw a special exception when trying to read from/write to a destroyed IndexStorage

    [ https://issues.apache.org/jira/browse/IGNITE-21750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827399#comment-17827399 ] 

Kirill Tkalenko commented on IGNITE-21750:
------------------------------------------

Looks good.

> 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
>  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)