Skip to content

[DOCS] Clarify that search timeouts behave like cancellation #31263

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
DaveCTurner opened this issue Jun 12, 2018 · 1 comment
Closed

[DOCS] Clarify that search timeouts behave like cancellation #31263

DaveCTurner opened this issue Jun 12, 2018 · 1 comment
Labels
>docs General docs changes help wanted adoptme :Search/Search Search-related issues that do not fall into other categories v6.2.4

Comments

@DaveCTurner
Copy link
Contributor

The documentation for the global search timeout setting does not describe how strictly the timeout applies. In fact, it seems that the timeout works on a polling basis, similarly to search cancellation, and therefore a search may take substantially longer than the configured timeout, and it may even do so successfully rather than timing out.

I think it'd be helpful to add this information to this documentation to clarify the situation.

@DaveCTurner DaveCTurner added >docs General docs changes help wanted adoptme :Search/Search Search-related issues that do not fall into other categories v6.2.4 labels Jun 12, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search-aggs

cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Sep 3, 2018
Global search timeouts and timeouts specified in the search request body use the
same internal mechanism as search cancellation. Therefore the same caveats
apply, mostly around the responsiveness of the timeout which gets only checked
by a running search on segment boundaries by default.

Closes elastic#31263
cbuescher pushed a commit that referenced this issue Sep 3, 2018
Global search timeouts and timeouts specified in the search request body use the
same internal mechanism as search cancellation. Therefore the same caveats
apply, mostly around the responsiveness of the timeout which gets only checked
by a running search on segment boundaries by default.

Closes #31263
cbuescher pushed a commit that referenced this issue Sep 3, 2018
Global search timeouts and timeouts specified in the search request body use the
same internal mechanism as search cancellation. Therefore the same caveats
apply, mostly around the responsiveness of the timeout which gets only checked
by a running search on segment boundaries by default.

Closes #31263
cbuescher pushed a commit that referenced this issue Sep 3, 2018
Global search timeouts and timeouts specified in the search request body use the
same internal mechanism as search cancellation. Therefore the same caveats
apply, mostly around the responsiveness of the timeout which gets only checked
by a running search on segment boundaries by default.

Closes #31263
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes help wanted adoptme :Search/Search Search-related issues that do not fall into other categories v6.2.4
Projects
None yet
Development

No branches or pull requests

2 participants