Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Hibernate search wont recover after reactor stopped

Description

Whenever the reactor stops it wont be able to recover itself and instead forever fail every elastic search request.

When failing it should instead recreate the connection to resume working, the only other solution is to completely restart the application

 

 

org.hibernate.search.util.common.SearchException: HSEARCH400007: Elasticsearch request failed: Request cannot be executed; I/O reactor status: STOPPED Request: POST /prod_prod-aws_ml_customer_v16/_search with parameters {from=0, size=5, track_total_hits=true} Response: (no response) at org.hibernate.search.backend.elasticsearch.work.impl.AbstractNonBulkableWork.lambda$execute$2(AbstractNonBulkableWork.java:60) at org.hibernate.search.util.common.impl.Futures.lambda$handler$1(Futures.java:63) at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990) at java.base/java.util.concurrent.CompletableFuture.uniExceptionallyStage(CompletableFuture.java:1008) at java.base/java.util.concurrent.CompletableFuture.exceptionally(CompletableFuture.java:2364) at org.hibernate.search.backend.elasticsearch.work.impl.AbstractNonBulkableWork.execute(AbstractNonBulkableWork.java:52) at org.hibernate.search.backend.elasticsearch.orchestration.impl.ElasticsearchSimpleWorkOrchestrator$WorkExecution.execute(ElasticsearchSimpleWorkOrchestrator.java:66) at org.hibernate.search.backend.elasticsearch.orchestration.impl.ElasticsearchSimpleWorkOrchestrator.doSubmit(ElasticsearchSimpleWorkOrchestrator.java:40) at org.hibernate.search.backend.elasticsearch.orchestration.impl.ElasticsearchSimpleWorkOrchestrator.doSubmit(ElasticsearchSimpleWorkOrchestrator.java:16) at org.hibernate.search.engine.backend.orchestration.spi.AbstractWorkOrchestrator.submit(AbstractWorkOrchestrator.java:135) at org.hibernate.search.backend.elasticsearch.orchestration.impl.ElasticsearchSimpleWorkOrchestrator.submit(ElasticsearchSimpleWorkOrchestrator.java:29) at org.hibernate.search.backend.elasticsearch.search.query.impl.ElasticsearchSearchQueryImpl.fetch(ElasticsearchSearchQueryImpl.java:124) at org.hibernate.search.backend.elasticsearch.search.query.impl.ElasticsearchSearchQueryImpl.fetch(ElasticsearchSearchQueryImpl.java:48)

Activity

Yoann RodièreOctober 23, 2023 at 12:19 PM

Hey , did you manage to reproduce this issue reliably in the end?

Patrick HilgenstockMay 3, 2022 at 9:23 AM

Alright - thank you for your effort.

Ill come back if we somehow manage to find any more information

Yoann RodièreApril 28, 2022 at 7:10 AM

That’s a shame I’d really like to get to the bottom of this, but it’s going to be hard if we have no idea how the problem arises in the first place.

For what it’s worth, it seems you’re not alone; other users of the Elasticsearch REST client (without Hibernate Search) have apparently experienced the same problem:

Nobody seems to have found a solution except to restart the application, though

Patrick HilgenstockApril 27, 2022 at 11:24 AM

I am sadly out of ideas how to reproduce it beyond that

Patrick HilgenstockApril 27, 2022 at 11:15 AM

Sorry Yoann, I was unable to look into this earlier

I just tried to reproduce it using docker pause/unpause which was sadly not successfull.

Details

Assignee

Reporter

Components

Affects versions

Priority

Created April 20, 2022 at 9:10 AM
Updated December 3, 2024 at 7:39 AM