[SOLR-9836] Add more graceful recovery steps when failing to create SolrCore

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.7, 7.0
• Component/s: SolrCloud
• Assignee: Mark Miller
• Reporter: Mike Drob
• Created: 07/Dec/16 18:57
• Updated: 23/Oct/19 19:38
• Resolved: 23/Oct/19 19:38

Description

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.

Issue Links

• depends upon: LUCENE-7592 EOFException while opening index should be rethrown as CorruptIndexException
• is related to: SOLR-10259 admin/cores?action=STATUS returns 500 when a single core has init failures
• relates to: SOLR-10006 Cannot do a full sync (fetchindex) if the replica can't open a searcher