[ https://issues.apache.org/jira/browse/SOLR-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753330#comment-15753330 ]
Mark Miller commented on SOLR-9836: ----------------------------------- bq. Possibly best to have two options The third option is not very difficult. Lucene already loads the last segments file it can. So if we get a corrupt index, we can just sanity check that the segments file can be loaded. If it can't, we can't fix things anyway, so recover. If the segments file looks fine, don't recover because the index could be corrected. > 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, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org