lucene-dev mailing list archives

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


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message