The documents should be implicitly committed when the Lucene index is closed.
When you perform a graceful shutdown, the Lucene index gets closed and the documents get committed implicitly. When the shutdown is abrupt as in a KILL -9, then this does not happen and the updates are lost. You can use the auto commit parameter when sending your updates so that the changes are saved right away, thought this could slow down the indexing speed considerably but I do not believe there are parameters to keep those un-commited documents "alive" after a kill. On Mon, Oct 18, 2010 at 2:46 PM, Ezequiel Calderara <ezech...@gmail.com>wrote: > Hi, i'm new in the mailing list. > I'm implementing Solr in my actual job, and i'm having some problems. > I was testing the consistency of the "commits". I found for example that if > we add X documents to the index (without commiting) and then we restart the > service, the documents are commited. They show up in the results. This is > interpreted to me like an error. > But when we add X documents to the index (without commiting) and then we > kill the process and we start it again, the documents doesn't appear. This > behaviour is the one i want. > > Is there any param to avoid the auto-committing of documents after a > shutdown? > Is there any param to keep those un-commited documents "alive" after a > kill? > > Thanks! > > -- > ______ > Ezequiel. > > Http://www.ironicnet.com <http://www.ironicnet.com/> > -- °O° "Good Enough" is not good enough. To give anything less than your best is to sacrifice the gift. Quality First. Measure Twice. Cut Once. http://www.israelekpo.com/
