You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2013/01/15 21:22:13 UTC
[jira] [Updated] (SOLR-3888) need beter handling of external
add/commit requests during tlog recovery
[ https://issues.apache.org/jira/browse/SOLR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe updated SOLR-3888:
-----------------------------
Fix Version/s: (was: 4.1)
4.2
> need beter handling of external add/commit requests during tlog recovery
> ------------------------------------------------------------------------
>
> Key: SOLR-3888
> URL: https://issues.apache.org/jira/browse/SOLR-3888
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Hoss Man
> Assignee: Yonik Seeley
> Fix For: 4.2
>
>
> as noted in SOLR-3884: if Solr suffers an unclean-shutdown with documents in the tlog that have not been hard commited to the index, it is then possible that on the next startup tlog recovery will cause "commits" sent by external clients (ie: after indexing new documents) to be ignored.
> in general, we need to give more thought to edge causes of how updates during tlog recovery should be dealt with...
> * is there a non-solrcloud tlog recovery case we're handling poorly?
> * should all updates be blocked until tlog recovery finishes?
> * should tlog recovery be synchronized on UpdateHandler init so that solr isn't even listing on the port until it finishes?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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