April 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-3900) 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.

by Ronak S (JIRA)

Ronak S ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ea56c8... ) *commented* on HSEARCH-3900 ( https://hibernate.atlassian.net/browse/HSEARCH-3900?atlOrigin=eyJpIjoiOGN... ) 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=eyJpIjoiOGN... ) Ok, but we are only using elastic search indexes. And on one application we are only pointing it to one elaticsearch cluster that is locally on that box only. So as far as I know, we are not mixing these two things. As I’ve not provided any local file directory for lucene under the hibernate config. And hibernate config only points to a single elastic search cluster. Also please look below in the snapshot of my local tomcat server. You can see hibernate search threads. These threads keep on running intermittently and never stops. You can also see one sync consumer thread for TBWC30 index, just like this we also see threads for other indexes and these keeps on going. ( 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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (OGM-1572) Update MongoDB Java Driver to version 3.11.2

by Davide D'Alto (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3900) 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.

by Yoann Rodière (JIRA)

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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3900) 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.

by Ronak S (JIRA)

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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3900) 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.

by Yoann Rodière (JIRA)

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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3902) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOWY5ZTZk... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiOWY... ) HSEARCH-3902 ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiOWY... ) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiOWY... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is only about SPIs, no new feature will be directly exposed as a result of this ticket. First, we need to expose addOrUpdate on the PojoIndexer if we want to implement a mass indexer that works correctly with concurrent updates. We need this in Infinispan in particular. Second, in Infinispan, indexing operations are always about a single entity/document, and contained types are irrelevant. Also, there is no concept of session, so the session is implemented as a singleton. Thus indexing in Infinispan does not need the PojoIndexingPlan and its overhead; Infinispan could use the PojoIndexer directly, if only it exposed the missing operations (addOrUpdate/delete/purge). Ideally, we should also make the PojoIndexer and IndexIndexers thread-safe, so that Infinispan can use them as singletons. This means in particular fixing the lazy initialization we currently have in PojoIndexer. Maybe we should make the PojoIndexer type-scoped and initialize its delegates eagerly? That certainly wouldn't be a problem for the MassIndexer. Finally, we'd also need to support DocumentCommitStrategy/DocumentRefreshStrategy in PojoIndexer/IndexIndexer operations. It's quite possible that Infinispan will need to force commit for each write in some situations, however bad performance will be. Maybe we'll be able to improve on that by adding DocumentCommitStrategy.WAIT_FOR/DocumentRefreshStrategy.WAIT_FOR, in another PR. ( https://hibernate.atlassian.net/browse/HSEARCH-3902#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3902#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3902) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer

by Yoann Rodière (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-3902) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiY2NjN2Ew... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiY2N... ) HSEARCH-3902 ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiY2N... ) Expose addOrUpdate/delete/purge on IndexIndexer/PojoIndexer ( https://hibernate.atlassian.net/browse/HSEARCH-3902?atlOrigin=eyJpIjoiY2N... ) Issue Type: Task Assignee: Unassigned Components: backend-elasticsearch, backend-lucene, mapper-pojo Created: 28/Apr/2020 00:03 AM Fix Versions: 6.0.0.Beta-backlog-high-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) This is only about SPIs, no new feature will be directly exposed as a result of this ticket. First, we need to expose addOrUpdate on the PojoIndexer if we want to implement a mass indexer that works correctly with concurrent updates. We need this in Infinispan in particular. Second, in Infinispan, indexing operations are always about a single entity/document, and contained types are irrelevant. Also, there is no concept of session, so the session is implemented as a singleton. Thus indexing in Infinispan does not need the PojoIndexingPlan and its overhead; Infinispan could use the PojoIndexer directly, if only it exposed the missing operations (addOrUpdate/delete/purge). Ideally, we should also make the PojoIndexer and IndexIndexers thread-safe, so that Infinispan can use them as singletons. This means in particular fixing the lazy initialization we currently have in PojoIndexer. Maybe we should make the PojoIndexer type-scoped and initialize its delegates eagerly? That certainly wouldn't be a problem for the MassIndexer. ( https://hibernate.atlassian.net/browse/HSEARCH-3902#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3902#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125- sha1:29f7b81 )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13985) Gradle plugin does not enhance java sources related to compileGroovy task

by SIA s.p.a (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13986) SequenceHiLoGeneratorNoIncrementTest is not testing the right Optimiser

by Sanne Grinovero (JIRA)

4 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2020