Have a look at http://wiki.apache.org/solr/NearRealtimeSearch which will help you (in TRUNK/4.0) with an efficient in-memory handling of NRT changes. Combine this with CommitWithin for persisting to disk: http://wiki.apache.org/solr/CommitWithin.
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 13. des. 2011, at 14:34, peter_solr wrote: > Hi all, > > we are indexing real-time documents from various sources. Since we have > multiple sources, we encounter quite a number of duplicates which we delete > from the index. This mostly occurs within a short timeframe; deletes of > older documents may happen, but they do not have a high priority. Search > results do not need to be exactly reatime (they can be 1 minute or so > behind), but facet counts should be correct as we use them to visualize > frequencies in the data. We are now looking for a good commit/merge > strategy. Any advice? > > Thanks and best, > Peter > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582294.html > Sent from the Solr - User mailing list archive at Nabble.com.
