[
https://issues.apache.org/jira/browse/IGNITE-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-20126:
---------------------------------------
Description:
When a read is tried to be done from an index storage that is under
destruction/destroyed, the requesting transaction is to be failed with an error
like 'The plan is stale'.
When a write is done to such an index storage, nothing should happen (nothing
written, but the caller should not get any exception).
was:Before each read-from-index operation (like opening a scan cursor or
getting next batch of such a cursor), we should check whether the index
physically exists. If not, the operation must be failed and the current RW tx
must be aborted.
> Handle 'index storage is under destruction' on read/write
> ---------------------------------------------------------
>
> Key: IGNITE-20126
> URL: https://issues.apache.org/jira/browse/IGNITE-20126
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> When a read is tried to be done from an index storage that is under
> destruction/destroyed, the requesting transaction is to be failed with an
> error like 'The plan is stale'.
> When a write is done to such an index storage, nothing should happen (nothing
> written, but the caller should not get any exception).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
