Ok, more detail: I was testing using the NoMergePolicy in Solr. As
Hoss pointed out in another thread, NoMergePolicy has no 0-argument
constructor, and so throws an exception during loading the core.
When there is no existing data/index/ directory, Solr creates a new
index/ directory at the beginn
: There is now a data/index with a write lock file in it. I have not
: attempted to read the index, let alone add something to it.
: I start solr again, and it cannot open the index because of the write lock.
Lance, i can't reproduce using trunk r1033664 on Linux w/ext4 -- what OS &
Filesystem a
