You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And even if I put a 2 sec timeout, I have often requests that take more than 5 and even 10 seconds that does not time out. But sometime, I have some query that take under 2 sec and says timed out.
On the documentation it says;
timeout A search timeout, bounding the search request to be executed within the specified time value and bail with the hits accumulated up to that point when expired. Defaults to no timeout.
With that I'm expecting every query to be under (or roughly) around 2 second, but not 5 or 10 seconds.
The text was updated successfully, but these errors were encountered:
Sadly, it is a best effort timeout, its not being checked on all places. Specifically, if you send a query that ends up being rewritten into many terms (fuzzy, or wildcard), that part (the rewrite part) does not check for a timeout.
I have seen many issues related to that, but nobody seems to have found an answer to this one, so I'm opening a new issue.
This is what I'm doing in the Java API for search;
https://gist.github.com/4444788
And even if I put a 2 sec timeout, I have often requests that take more than 5 and even 10 seconds that does not time out. But sometime, I have some query that take under 2 sec and says timed out.
On the documentation it says;
timeout A search timeout, bounding the search request to be executed within the specified time value and bail with the hits accumulated up to that point when expired. Defaults to no timeout.
With that I'm expecting every query to be under (or roughly) around 2 second, but not 5 or 10 seconds.
The text was updated successfully, but these errors were encountered: