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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2025/03/27 11:09:00 UTC

[jira] [Updated] (IGNITE-24938) Ignore attempts to create index storage in destroyed table storage

     [ https://issues.apache.org/jira/browse/IGNITE-24938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated IGNITE-24938:
---------------------------------------
    Description: 
IGNITE-24926 requires a lot of time to fix. This one is a fast and dirty workaround for it.

The only problem that the race described in IGNITE-24926 causes is that, when creating an index storage (on index registration), we might get into a situation when the partition storage is already destroyed due to partition eviction initiated AFTER the index registration. The workaround is to quietly ignore such attempts.

> Ignore attempts to create index storage in destroyed table storage
> ------------------------------------------------------------------
>
>                 Key: IGNITE-24938
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24938
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> IGNITE-24926 requires a lot of time to fix. This one is a fast and dirty workaround for it.
> The only problem that the race described in IGNITE-24926 causes is that, when creating an index storage (on index registration), we might get into a situation when the partition storage is already destroyed due to partition eviction initiated AFTER the index registration. The workaround is to quietly ignore such attempts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)