Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3900 (
https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiN2F...
)
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=eyJpIjoiN2F...
)
As I explained at length in my answer to your stackoverflow question (
https://stackoverflow.com/questions/61405928/hibernate-search-creating-un...
) , setting autoregister_listeners to false disables Hibernate Search completely, and that
has been the case since Hibernate Search 5.5 at the very least. So this setting is
unlikely to have anything to do with your problem.
You're mentioning many refresh operations on Elasticsearch's side. Did you by any
chance set hibernate.search.default.elasticsearch.refresh_after_write to true ? Because
that's bound to hurt performance * *a lot* *. So much so that we explained you
shouldn't enable it in the documentation:
You should not rely on the synchronous behaviour for your production code
except in rare cases as Elasticsearch is optimised for asynchronous
writes: leave at false for optimal performance.
(
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:c966059 )