Hi, The error message does not exactly highlight the underlying cause of the failure (connection timeout, read timeout etc.), getting this sometimes when using with AWS RDS. What are the probable reasons for this error?

Please give the version of Hibernate Search you’re using, and copy/paste your logs here. Make sure to format logs properly, with a line containing only three backticks this before and after the logs: ``` logs go here ```

We are using 6.0.0.Beta7 Attaching logs: Unable to perform afterTransactionCompletion callback: HSEARCH800024: Automatic indexing failed after transaction completion: HSEARCH800022: Indexing failure: HSEARCH400588: The operation failed due to the failure of the call to the bulk REST API.. The foll…

I meant the full log, not the exception message. In Beta6 and above, you should get the exception thrown by the bulk work somewhere in your stack trace.

Ah right, I got it in the extended stacktrace: org.hibernate.search.util.common.SearchTimeoutException: HSEARCH400590: Request exceeded the timeout of 60s, 0ms and 0ns

Well then here is your answer. The indexing request couldn’t be handled in less than 60s, so Hibernate Search gave up. As to why the request couldn’t be handled in less than 60s… I don’t know. Maybe your Elasticsearch cluster is too slow: the servers are undersized (not enough CPU, disks too slo…

@yrodiere do you recon we will always have to enable auto discovery when using AWS elasticsearch (with multiple nodes)? Also, the IOPS consumed seem low enough, so maybe I will reduce the max_bulk_size and evaluate.

[image] Ansuman_Pattanayak: @yrodiere do you recon we will always have to enable auto discovery when using AWS elasticsearch (with multiple nodes)? If you want your requests to be routed to all nodes, I imagine you will? Not sure, though. Maybe AWS the URL assigned to the service points to ea…

Yes, I also imagined that the ES domain URL which AWS provides takes care of request handling for all the nodes under it. This issue was happening quite rarely before. Then we made a change to an entity which resulted in a nested storage for two of its fields. This drastically reduced the mass inde…

The operation failed due to the failure of the call to the bulk REST API

Hibernate Search

Topic		Replies	Views
HSEARCH400590: Request exceeded the timeout of 60s, 0ms and 0ns: - Error Hibernate Search	5	1831	June 30, 2020
Request timeout during index validation Hibernate Search	26	1353	July 27, 2022
HTTP request timeouts when using mass indexer Hibernate Search	2	619	February 16, 2022
Hibernate Search + Elastic Search indexing/search taking too much time Hibernate Search	1	929	March 25, 2021
Some data is not indexed. The error name is HSEARCH400007 Hibernate Search	1	1870	October 29, 2019

The operation failed due to the failure of the call to the bulk REST API

Related topics