Ronak S (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8...
) *commented* on HSEARCH-3900 (
https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiNGY...
)
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=eyJpIjoiNGY...
)
I’m really Sorry, I could not understand the below comments. could you please elaborate on
these. So I could point you to the info you need.
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?
And BTW do you want to say that we are pointing the same Elastic Search instance from two
different instances/or servers of our application?
(
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 )