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? Any new options for optimize to force flush to disk and remove write.lock? Regards Bernd
