Yes I'm going to add the "catch up" time and see if that works. Is there a way to force synchronous updates as there was in 2.x?
Yes I'll log an issue and attach my code. I'll continue to work it as well. Right now it looks like I can load a real world amount data by running batches, starting and stopping JBoss with each batch. But it would be great if this was eventually not necessary.
Thanks. Do you have to restart JBoss even when you obtain a new session, do a fixed amount of work, save, and then repeat?
I think there's always some degree of asynchronous-ness within Hibernate Search. It's far easier to just disable queries. (Though that won't give you representative results, it would at least tell you whether the slower memory leak is still there.)
I tried the delay, pausing 10 minutes to let indexing "catch up" and that made no difference, so it appears that something else is still leaking. At this point I'll clean up my test and submit the JIRA.
MODE-1793 created.