I noticed that while the full index is running, the incremental indexes fail with this exception:
lucene.JavaError: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/data/www/reviewboard/search-index/write.lock It looks like the default lock timeout is 1 second. Has this been noticed before? Any thoughts about preventing incremental indexing while the full index is running? Also, what's the motivation for doing the full index? Is it trying to pick up changes that aren't caught by checking the last_updated field? -Eric --~--~---------~--~----~------------~-------~--~----~ Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~----------~----~----~----~------~----~------~--~---
