-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Expose ignore_throttled
as an option for _msearch
#26244
Comments
Pinging @elastic/kibana-app |
ingore_throttled
as an option for _msearch
ignore_throttled
as an option for _msearch
As of a discussion with PMs we just decided, that we will add a new setting to Kibana "Search in Frozen index" (name is WIP), which will default to |
++ thanks @timroes |
@grabowskit @alexfrancoeur @tsg @tbragin above is our plan for frozen indices in Kibana. The first phase will include a global setting that enables search on frozen indices, in the future and based on feedback we might consider making this setting per index pattern. |
Thanks for the ping @AlonaNadler. If this is enabled, do we have to worry about client side timeouts at all? Do we need to consider any of these changes for reporting (CSV & PDF)? |
cc @makwarth @roncohen @alvarolobato FYI |
In elasticsearch starting with version 6.6 we have a new beta feature called frozen indices. Frozen indices will not be search on by default unless a the request option
ignore_throttled=false
is set. This is mainly to protect users from running slowish requests with a index pattern etc. Yet, frozen indices also have a protection that allows fast evaluation of date-ranges which makes it suitable for kibana since even if a pattern expands to a frozen index the query will be likely very fast unless it can match. Yet, before we enable anything by default we should at least have an option to opt-in to this feature similar to what we have done here This would allow folks to try frozen indices through kibana. Down the road we might even enable this feature by default.The text was updated successfully, but these errors were encountered: