-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Fix default search timeout in watcher docs #106404
Conversation
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-data-management (Team:Data Management) |
I think you are right that the documentation needs to change to 1m. Given that this is pretty minor and no one has noticed for at least 7 years, I think we only need to put this in |
It's also kind of odd that |
Looking in the old private x-pack repo, if the default value of |
💚 Backport successful
|
There are a couple of "default search timeout" settings:
elasticsearch/x-pack/plugin/watcher/src/main/java/org/elasticsearch/xpack/watcher/WatcherService.java
Line 99 in dceea61
elasticsearch/x-pack/plugin/watcher/src/main/java/org/elasticsearch/xpack/watcher/execution/TriggeredWatchStore.java
Line 71 in dceea61
These two do have a default of 30s, but they seem to be influencing other aspects of the watcher module.
The one that actually seems to be the Watcher search input default timeout setting is:
elasticsearch/x-pack/plugin/watcher/src/main/java/org/elasticsearch/xpack/watcher/input/search/SearchInputFactory.java
Line 36 in dceea61
This seems to have been the case for a while already (the docs line and the default in the code haven't changed since 2017), so then the question becomes until what version we want to backport this (provided that my conclusion above is actually correct).