Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3900 (
https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiMzR...
)
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=eyJpIjoiMzR...
)
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.
Hibernate Search offers you two ways of indexing:
* Directly into an embedded Lucene instance, where indexes are stored locally
* OR Into a remote Elasticsearch cluster
You seem to be using both.
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?
No, I was saying you may have multiple instances of your application running. But that was
wrong; I forgot that in Search 5 you can configure each index to use either Lucene or
Elasticsearch. Apparently you configured *some* indexes to use Elasticsearch, but not all
of them. That's fine if that's what you really wanted to do.
(
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 )