On Wed, Oct 17, 2012 at 9:33 AM, Bernd Fehling <bernd.fehl...@uni-bielefeld.de> wrote: > Hi list, > > while checking the runtime behavior of solr 4.0.0 I recognized that the > handling > of write.lock seams to be different. > > With solr 3.6.1 after calling optimize the index is optimzed and write.lock > removed. > This tells me everything is flushed to disk and its save to copy the index. > > With solr 4.0.0 after calling optimize the index is optimized but the > write.lock remains. > > They both use NativeFSLockFactory. > > What could be the cause that write.lock remains with solr 4.0.0?
The IndexWriter is left open now on optimizes / commits to enable better NRT and better concurrency with adds (commits no longer block adds). -Yonik http://lucidworks.com
