Right, there is no need for that locking, you can safely have multiple indexing/update requests hitting Solr in parallel.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Andrew Savory <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Friday, May 9, 2008 1:24:06 PM > Subject: Re: Weird problems with document size > > Hi, > > On 09/05/2008, Otis Gospodnetic wrote: > > > I don't understand what that lock and unlock is for... > > Just do this: > > add > > add > > add > > add > > ... > > ... > > optionally commit or optimize > > Yeah, I didn't understand what the lock/unlock was for either - but on > further reviewing the code, we have a wrapper around the solr servlet > which does a crude type of locking to ensure only one index updater > process can run at a time. Not sure it's needed, as I'd guess that > solr would handle things gracefully anyway, but it at least stops > multiple index clients firing up. > > Meanwhile it seems that these documents can successfully be added to > solr when it is running in jetty, so I'm now trying to find out what > Tomcat is doing to break things. > > Thanks for the reply, > > > Andrew.
