[
https://issues.apache.org/jira/browse/SOLR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated SOLR-3888:
------------------------------------
Component/s: SolrCloud
> 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
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Hoss Man
> Assignee: Yonik Seeley
> Fix For: 4.9, 6.0
>
>
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
