On 9/3/2015 10:00 PM, Renee Sun wrote: > unfortunately we are still using solr 3.5 with lucene 2.9.3 :-( If we > upgrade to solr 4.x it will require upgrade of lucene away from 2.x.x > which will need re-index of all our data. With current measures, it > might take about 8-9 for the data we have to be re-indexed, a big > concern.
Solr 3.5 should include Lucene 3.5, and I expect it might have some serious problems running if you tried to replace the Lucene jars in the .war file with 2.x versions. What evidence do you have that it's running Lucene 2.x? Solr 4.x can use a 3.x index. I believe that Solr 1.5 (which was never released) included a 2.9 version of Lucene. Solr 1.4 certainly did. > so to understand autocommit better, since it says: > > <maxTime>300000</maxTime> > > I want to know > > 1) if I have a batch of 2000 documents being added to index, it may > span of 3 minutes to index all 2000 document. Will the autocommit > defined above kick off a commit 5 minutes after the first of 2000 > document being indexed? > > 2) the autocommit will NOT commit if there is no update in last 5 > minutes? > > 3) will maxTime counts in the document deletion or it only cares > about adding a document? In another word, should I use > maxPendingDeletes for document deletion? I cannot find any complete information about what maxPendingDeletes does, except that it can affect memory usage. I believe that this setting is no longer there in 4.x, which is probably why I can't find anything. The way I understand autocommit relative to your questions: With a maxTime of five minutes, if it takes three minutes to index your documents, the commit should happen two minutes after the last document is indexed. *Any* change to the index will start the autoCommit timer, including deletes. If the index hasn't been updated, autoCommit will not do anything. Thanks, Shawn
