[ https://issues.jboss.org/browse/ISPN-3767?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-3767: ------------------------------------- Romain, you do not say on which version you're running. The first branch you sent was based on an old 6 (mid October) and the second on 5.2.4. I would recommend migrating to 6.0.0.Final. Also, let's keep the mass indexing on a one-node cluster being broken and indexing slowness as separate issues. Looking at the first branch, it's quite old, so I applied the same changes on current version of DistributedMassIndexingTest. Running it with 1 or 2 nodes fails the asserts right after the index rebuild. Running with 3, 4, 5 ... nodes works. A quick analysis leads me to believe it's caused by indexing not being fully synchronous. MassIndexer.start() should only return after the index was rebuilt, but unfortunately it seems to return right after reindexing work was performed but without any guarantee it was actually flushed. I'll fix this during this week. Right now, a quick workaround to confirm this : replace enqueueAsyncWork with doWorkInSync at https://github.com/infinispan/infinispan/blob/master/query/src/main/java/... This is not the clean fix, just a workaround to confirm the root of the problem. Should I also look at branch number 2 or is this clarified? The commit message being "modify DistributedMassIndexingTest to show slowlyness of indexing" makes me think it's about a different issue :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira