[jira] [Resolved] (ASTERIXDB-3226) Crash loop on leaked secondary index files

["Murtadha Makki Al Hubail (Jira)" <ji...@apache.org>]

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

Murtadha Makki Al Hubail resolved ASTERIXDB-3226.
-------------------------------------------------
    Resolution: Fixed

> Crash loop on leaked secondary index files
> ------------------------------------------
>
>                 Key: ASTERIXDB-3226
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3226
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>    Affects Versions: 0.9.8
>            Reporter: Murtadha Makki Al Hubail
>            Assignee: Murtadha Makki Al Hubail
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> When some secondary index files are leaked after its primary is dropped, an NC will be in a crash loop after a restart due to the startup checkpoint task attempting to flush all registered indexes and we halt on missing primary during flush. Since there are scenarios where secondary index files can be leaked, we should warn rather than halt. Eventually, when all NCs complete their startup, the global storage cleanup will remove such indexes.



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