Thanks Mike and Yonik! I've upgraded the project to trunk Solr,
added in the SingleInstanceLockFactory setting and bumped the write
lock timeout. I personally haven't duplicated the issue (all works
fine on my development box) but the client will give it a try in
their test environment soon and I'll report back if issues persist.
Erik
On Aug 6, 2007, at 4:38 PM, Yonik Seeley wrote:
On 8/6/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
<writeLockTimeout>1000</writeLockTimeout>
Have you tried upping this? The problem might be that you are
commiting every 1.0s, and a single commit eventually might take
longer than this (and you're only waiting 1.0s to acquire the write
lock).
With all the locking done in Solr, I thought it shouldn't be possible
to get a write lock timeout except on startup. Perhaps it's related
to this:
https://issues.apache.org/jira/browse/SOLR-240
Erik - you could perhaps try SingleInstanceLockFactory or native FS
locks in the trunk version and see if that fixes the issue.
-Yonik
