[
https://issues.apache.org/jira/browse/SOLR-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086986#comment-13086986
]
Michael McCandless commented on SOLR-2565:
------------------------------------------
+1 to backport; this is a serious limitation in Solr.
ElasticSearch has been using this approach (NRT & commit, not IW.close) for
quite some time already.
> Prevent IW#close and cut over to IW#commit
> ------------------------------------------
>
> Key: SOLR-2565
> URL: https://issues.apache.org/jira/browse/SOLR-2565
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 4.0
> Reporter: Simon Willnauer
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2565.patch, SOLR-2565.patch, SOLR-2565.patch
>
>
> Spinnoff from SOLR-2193. We already have a branch to work on this issue here
> https://svn.apache.org/repos/asf/lucene/dev/branches/solr2193
> The main goal here is to prevent solr from closing the IW and use IW#commit
> instead. AFAIK the main issues here are:
> The update handler needs an overhaul.
> A few goals I think we might want to look at:
> 1. Expose the SolrIndexWriter in the api or add the proper abstractions to
> get done what we now do with special casing:
> 2. Stop closing the IndexWriter and start using commit (still lazy IW init
> though).
> 3. Drop iwAccess, iwCommit locks and sync mostly at the Lucene level.
> 4. Address the current issues we face because multiple original/'reloaded'
> cores can have a different IndexWriter on the same index.
> Eventually this is a preparation for NRT support in Solr which I will create
> a followup issue for.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
