On Wed, May 27, 2009 at 5:49 AM, Michael McCandless
<luc...@mikemccandless.com> wrote:
> Hmm... so in fact it looks like Solr had done a number of commits
> already (especially, given how large your generation is -- the "cje"
> in segments_cje means there were a number of commits).
>
> Were there any other exceptions leading up to this? Disk full?
> Anything unusual in your Solr configuration?
>
> Is there any chance that a 2nd Solr core attempted to access this same
> directory?
Solr uses SingleInstanceLockFactory by default... so Solr cores (in a
multi-core env) would be protected.
But maybe we should switch to NativeFSLockFactory to be safe from
other processes (with the downside that it will fail for some
filesystems).
<!--
This option specifies which Lucene LockFactory implementation to use.
single = SingleInstanceLockFactory - suggested for a read-only index
or when there is no possibility of another process trying
to modify the index.
native = NativeFSLockFactory
simple = SimpleFSLockFactory
(For backwards compatibility with Solr 1.2, 'simple' is the default
if not specified.)
-->
<lockType>single</lockType>
-Yonik
http://www.lucidimagination.com
