Skip to content
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

[DOC] Documentation for search.cancel_after_time_interval and search.default_search_timeout parameters is incorrect #6843

Closed
1 of 4 tasks
jainankitk opened this issue Apr 2, 2024 · 0 comments
Labels
3 - Done Issue is done/complete

Comments

@jainankitk
Copy link
Contributor

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
While the documentation is correctly listed on the url parameters reference - https://opensearch.org/docs/2.12/api-reference/search/#url-parameters, the documentation for search.cancel_after_time_interval and search.default_search_timeout parameters looks swapped with each other. The correct documentation should be:

search.cancel_after_time_interval (Dynamic, time unit): A cluster-level setting that sets the default timeout for all search requests at the coordinating node level. If the timeout is specified in the search request, it takes precedence over this setting. Default is -1 (no timeout).

search.default_search_timeout (Dynamic, time unit): A cluster-level setting that specifies the maximum amount of time that a search request can run before it is canceled at the shard level. After this time has been reached, a request is stopped and all associated tasks are canceled. Default is -1.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Location - https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/search-settings/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete
Projects
None yet
Development

No branches or pull requests

2 participants