Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3900 (
https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNDk...
)
Re: drop-and-create strategy is not working at app. startup when
"hibernate.search.autoregister_listeners" is set to false. And if true, startup
index creation thread are not released, sending the app in out of memory. (
https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNDk...
)
Thank you.
From what I can see, the threads are not doing anything. They are just waiting for work.
These threads are necessary for the operation of Hibernate Search; they will be there for
the whole time your application is up. Most of the time they won't do anything and can
be safely ignored.
Why do you think these threads are a problem?
By the way, the second thread dump has
org.hibernate.search.backend.impl.lucene.SyncWorkProcessor in the stack trace, which
indicates you are also running a Lucene backend * *on top of* * the Elasticsearch backend.
This typically can only happen if you have two instances of Hibernate Search running,
which should only happen if you have two instances of your application running with
different configuration. Is that on purpose?
(
https://hibernate.atlassian.net/browse/HSEARCH-3900#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-3900#add-comment?atlOrigin...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )