Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *updated* an issue
Hibernate Search (
https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNmM5MGJk...
) / Task (
https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiNmM...
) HSEARCH-2505 (
https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiNmM...
) Lower the default read timeout with Elasticsearch (
https://hibernate.atlassian.net/browse/HSEARCH-2505?atlOrigin=eyJpIjoiNmM...
)
Change By: Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
)
We currently have a very high value of 60s, due to calls to the health API where we indeed
may have to wait this long.
-If per-request timeouts are added to Jest
(
https://github.com/searchbox-io/Jest/issues/411), we could use that instead and avoid
this high default read timeout.-
~ We asked for per-request timeouts to be added to the official Elasticsearch client, so
let's wait for that first. ~
It looks like it's not going to happen. Let's try another way: use a lower read
timeout by default, but implement health checks in Hibernate Search so that we try again
on read timeout, until the health check timeout is reached.
(
https://hibernate.atlassian.net/browse/HSEARCH-2505#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-2505#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#100140- sha1:fbb0377 )