There aren't any other nodes involved in the cluster. This is the 'just
make it work' phase of the project, so the simplest configuration is being
Note that normal index access is fine. Entity operations populate the
Lucene indexes as expected, and search operations work as expected. It is
only the MassIndexer that has had trouble to this point.
On Fri, Aug 26, 2011 at 7:02 AM, Sanne Grinovero <sanne(a)hibernate.org>wrote:
the MassIndexer needs to acquire the Directory lock, which is in this
case distributed, i.e. it's a single lock to coordinate writes across
all nodes (searches can happen in parallel, but writes can not).
Is it possible that another node is writing to the index, or is any
node using exclusive_index_use=true ?
2011/8/25 Tom Waterhouse <tomwaterhouse(a)gmail.com>:
> I'm trying to setup clustering of entities and Lucene indexes for our app
> with Hibernate 3.6.5, Hibernate Search 3.4.0, Infinispan 5.0. I'm using
> FileCacheStore for the Infinispan cache loader
> MassIndexerImpl.startAndWait() never returns with this configuration. A
> lock is never able to be obtained, see the stack from a thread dump
> The same MassIndexer call works fine when using FSDirectoryProvider.
> Should MassIndexer work with Infinispan as the directory?
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.lucene.store.Lock.obtain(Lock.java:91)
> at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1097)
> - locked <7793180e8> (a org.hibernate.search.backend.Workspace)
> hibernate-dev mailing list