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. |
|