Skip to content

Timeout on search not respected #2520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jgagnon1 opened this issue Jan 3, 2013 · 1 comment
Closed

Timeout on search not respected #2520

jgagnon1 opened this issue Jan 3, 2013 · 1 comment

Comments

@jgagnon1
Copy link

jgagnon1 commented Jan 3, 2013

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.

@kimchy
Copy link
Member

kimchy commented Jan 6, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants