lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3179) handle commit failures
Date Wed, 29 Feb 2012 13:31:56 GMT

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

Yonik Seeley commented on SOLR-3179:
------------------------------------

Specific to a commit failure, we probably shouldn't try to do peersync or log replay or anything,
but should go straight to replication?

One issue I've hit in the tests is that a commit may fail currently, but updates continue
to succeed because they are simply buffered in memory.  Seems like it would be a good idea
of we could recognize that we are in real trouble ASAP.
                
> handle commit failures
> ----------------------
>
>                 Key: SOLR-3179
>                 URL: https://issues.apache.org/jira/browse/SOLR-3179
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Yonik Seeley
>
> We may be able to be more proactive about handing some failures (like a commit failure).
 In cloud mode, we should probably mark ourselves down and put ourselves in recovery mode?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message