lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9836) Add more graceful recovery steps when failing to create SolrCore
Date Fri, 16 Dec 2016 17:21:59 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755004#comment-15755004
] 

Mike Drob commented on SOLR-9836:
---------------------------------

bq. This should already be Lucene's behavior. I assume if it's not falling back it's because
there is no previous segments file to fall back to. 
I didn't see Lucene doing this. Or at least, I didn't see Solr leverage Lucene to do this.
Both through manual inspection of the code and through testing via {{MissingSegmentRecoveryTest::testRollback}}
in my patch.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message