[
https://issues.apache.org/jira/browse/SOLR-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494554#comment-13494554
]
Otis Gospodnetic commented on SOLR-3816:
----------------------------------------
Hmmmm... didn't check the sources now, but I'm not sure if the above is all
correct. Lucene gets the new Reader from IndexWriter, and I would think Solr
uses that on soft commit and not something else, big and heavy. Yes, there is
Searcher/cache warming, but I'm not sure if that comes into play any more with
NRT and soft commits.
> Need a more granular nrt system that is close to a realtime system.
> -------------------------------------------------------------------
>
> Key: SOLR-3816
> URL: https://issues.apache.org/jira/browse/SOLR-3816
> Project: Solr
> Issue Type: Improvement
> Components: clients - java, replication (java), search,
> SearchComponents - other, SolrCloud, update
> Affects Versions: 4.0
> Reporter: Nagendra Nagarajayya
> Labels: nrt, realtime, replication, search, solrcloud, update
> Attachments: alltests_passed_with_realtime_turnedoff.log,
> SOLR-3816_4.0_branch.patch, SOLR-3816-4.x.trunk.patch,
> solr-3816-realtime_nrt.patch
>
>
> Need a more granular NRT system that is close to a realtime system. A
> realtime system should be able to reflect changes to the index as and when
> docs are added/updated to the index. soft-commit offers NRT and is more
> realtime friendly than hard commit but is limited by the dependency on the
> SolrIndexSearcher being closed and reopened and offers a coarse granular NRT.
> Closing and reopening of the SolrIndexSearcher may impact performance also.
--
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: [email protected]
For additional commands, e-mail: [email protected]
