Our application runs on Tomcat and uses Hibernate for JPA, and Hibernate Search to provide full text search. It needs to run in cluster environment therefore after ready the Hibernate Search documentation I decided to configure Infinispan as the directory provider and JGroups as a backend.

First of all it's not very clear to me whether I need two JGroups configuration - one for Infinispan and one for the backend or will it use the same?

And the problem I'm facing with:
I'm observing is that when I update an entity (that is visible on both nodes) on node1 the changes are visible on both node1 and node2, however if I create an entity on node1 the changes are visible only on node2 (the other).

I update an entity that is visible only on node2 the changes are visible only on node2, the entity remains invisible for node1

If i create an entity on node2 the changes are again visible only on node2. If I update and entity on node2 then the changes are visible on both nodes.

This sounds similar to a master/slave replication where the changes are written to the master only, but this is true only in case I create an entity (INSERT), not if I modify (UPDATE) an existing one.

Versions:
Hibernate Search 4.3.0
Infinispan 5.2.5
JGroups 3.2.7

What could be the cause of this behavior?

That is correct, Infinispan just happens to use JGroups as well and the two configurations (and channels) are created and used independently. You might actually want to make sure the two cluster names are different so that the two cluster groups are isolated from each other.

I never heard of a problem like you describe, I suspect a configuration mistake? To clarify, you do indeed need to configure the nodes in a master/slave configuration: only one node writes to the index, and the other node needs to forward requests using the jgroups backend. The node writing should NOT use the NRT backend, since this doesn't flush all writes immediately.



It would be very helpful if you could share a test or demo app? In case you are interested in the tests, I'd encourage you to look into the source code to see how we write tests, it's quite simple and there are plenty of helpers to reuse.



These are quite old versions. Would you be able to verify that you're not hitting a solved problem by updating to our latest stable release?

Hibernate Search 4.5.1.Final
Infinispan 6.0.2.Final
JGroups 3.4.3.Final
Hibernate ORM 4.3.5.Final

Final thought:
could you also try to set
hibernate.search.​enable_dirty_check = false
if that helps, the problem is not clustering related at all.. ;-)

HTH

Hi Sanne,

thanks for the response and the clarification. After I understood that I need two separate JGroups config (and configured Hibernate Search to use jgoups as backend) the setup went easily. Maybe the documentation could contain a notice about having separate JGroups config.

Thanks!
Andras

Hi Andras, good point. I'm actually working to simplify all of the clustered setups, but if I don't finish on time for 5.0 I'll at least clarify that in the docs.