[jira] [Updated] (SOLR-9836) Add more graceful recovery steps when failing to create SolrCore

["Mike Drob (JIRA)" <ji...@apache.org>]

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

Mike Drob updated SOLR-9836:
----------------------------
    Attachment: SOLR-9836.patch

Attaching a first attempt at improving this behaviour.

Some open discussion points -
* Do we want to expand this for other types of failures? I think yes, but in a future iteration/JIRA.
* Would it be safe to add {{directoryFactory.doneWithDirectory()}} to {{modifyIndexProps}}
* Should {{modifyIndexProps}} stay in {{IndexFetcher}} or move somewhere more generic?


> Add more graceful recovery steps when failing to create SolrCore
> ----------------------------------------------------------------
>
>                 Key: SOLR-9836
>                 URL: https://issues.apache.org/jira/browse/SOLR-9836
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Mike Drob
>         Attachments: SOLR-9836.patch
>
>
> I have seen several cases where there is a zero-length segments_n file. We haven't identified the root cause of these issues (possibly a poorly timed crash during replication?) but if there is another node available then Solr should be able to recover from this situation. Currently, we log and give up on loading that core, leaving the user to manually intervene.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org