Re: Strategy --> Frequent updates in our application

2011-06-03 Thread Otis Gospodnetic
r-user@lucene.apache.org > Sent: Fri, June 3, 2011 2:10:27 PM > Subject: Re: Strategy --> Frequent updates in our application > > On Jun 2, 2011, at 8:29 PM, Naveen Gupta wrote: > > > and what about NRT, is it fine to apply in this case of scenario > > Is NRT re

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread Jack Repenning
On Jun 2, 2011, at 8:29 PM, Naveen Gupta wrote: > and what about NRT, is it fine to apply in this case of scenario Is NRT really what's wanted here? I'm asking the experts, as I have a situation not too different from the b.p. It appears to me (from the dox) that NRT makes a difference in the

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread Erick Erickson
Do be careful how often you pull down indexes on your slaves. A too-short polling interval can lead to some problems. Start with, say, 5 minutes and insure that your autowarm time (see your logs) is less than your polling interval Best Erick On Fri, Jun 3, 2011 at 8:43 AM, pravesh wrote: >

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread pravesh
You can go ahead with the Master/Slave setup provided by SOLR. Its trivial to setup and you also get SOLR's operational scripts for index synch'ing b/w Master-to-Slave(s), OR the Java based replication feature. There is no need to re-invent other architecture :) -- View this message in context:

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread Nagendra Nagarajayya
Hi Naveen: Solr with RankingAlgorithm supports NRT. The performance is about 262 docs / sec. You can get more information about the performance and NRT from here: http://solr-ra.tgels.com/wiki/en/Near_Real_Time_Search You can download Solr with RankingAlgorithm from here: http://solr-ra.tgels

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread Naveen Gupta
Hi Pravesh We don't have that setup right now .. we are thinking of doing that for writes we are going to have one instance and for read, we are going to have another... do you have other design in mind .. kindly share Thanks Naveen On Fri, Jun 3, 2011 at 2:50 PM, pravesh wrote: > You c

Re: Strategy --> Frequent updates in our application

2011-06-03 Thread pravesh
You can use DataImportHandler for your full/incremental indexing. Now NRT indexing could vary as per business requirements (i mean delay cud be 5-mins ,10-mins,15-mins,OR, 30-mins). Then it also depends on how much volume will be indexed incrementally. BTW, r u having Master+Slave SOLR setup? -- V

Re: Strategy --> Frequent updates in our application

2011-06-02 Thread Otis Gospodnetic
Naveen, Solr does support incremental indexing. Solr currently doesn't make use of Lucene's NRT support, but that is starting to change. If you provide more specifics about issues you are having and your architecture, data and query volume, we may be able to help better. Otis Sematext :