I set a breakpoint inside of org.apache.lucene.store.Lock.obtain(long) and
noticed something peculiar - the method is called twice. The first call
succeeds, the second fails, my guess because the first call obtained the
I added logging/stepped through our code to verify that we only make the
call one time, and in fact that is the case.
We are using JPA and JTA, would that impact the call to obtain the lock in
such a way as to allow two calls?
Here is the call we make, including the logging statements I've added. This
call is done inside of a JTA transaction.
FullTextEntityManager fullTextEntityManager =
MassIndexer massIndexer =
On Sun, Aug 28, 2011 at 9:28 AM, Sanne Grinovero <sanne(a)hibernate.org>wrote:
I've created a test checking for both event-driven changes and the
MassIndexer, double-checking event-driven changes after the
MassIndexer completion, starting two nodes initially and adding a
third node dynamically during the test execution.. alls seems to work
flawlessly, a part of taking so long due the jgroups delays for
starting a new node (it takes ~14 seconds to run).
you can find it here:
Could you please check this test out and change it as much as you feel
is needed to reproduce the problem?
Also note the previous commit to change the Infinispan version to 5.0:
you mentioned you're using 5.0 but Search 3.4 was intended to support
Infinispan 4.2.x, so I had to apply some minimal changes.
You might want to try out Hibernate Search 4.0.0.Alpha1, intended to
support Infinispan 5.x, but I've created this test for Search 3.4 as
the backends interaction in 4.0 is very different: there are not two
competing backends anymore, but a unified access to the IndexWriter,
so to try reproducing your issue it was pointless to try it out on
2011/8/27 Tom Waterhouse <tomwaterhouse(a)gmail.com>:
> 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
> Note that normal index access is fine. Entity operations populate the
> Lucene indexes as expected, and search operations work as expected. It
> 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>
>> Hi Tom,
>> 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
>> > FileCacheStore for the Infinispan cache loader
>> > (InfinispanDirectoryProvider).
>> > MassIndexerImpl.startAndWait() never returns with this configuration.
>> > lock is never able to be obtained, see the stack from a thread dump
>> > below.
>> > The same MassIndexer call works fine when using FSDirectoryProvider.
>> > Should MassIndexer work with Infinispan as the directory?
>> > Tom
>> > 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
>> > at
>> > at
>> > - locked <7793180e8> (a org.hibernate.search.backend.Workspace)
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev