Impact of setting max_inner_result_window at index level


We have a user index and it has recipients (nested object).
Since recipients are saved in User domain as nested object, so in order to pull the recipients data with pagination we are using inner_hits query in respective API codebase.

The solution provided in the error message suggests changing the "index.max_inner_result_window" setting.
But while going through some documentation found that this change would have a performance hit.

Kindly provide the recommendation to fix below issue?

When we reach the page no 3, the from value will be 100 and size =50 (considering default page size which is 50), the ES gives below error message -

"type": "illegal_argument_exception",
"reason": "Inner result window is too large, the inner hit definition's [null]'s from + size must be less than or equal to: [100] but was [150]. This limit can be set by changing the [index.max_inner_result_window] index level setting."

In order to fix the error message, it is suggesting us to change the index level setting’s [index.max_inner_result_window] to support more than 100 records.

Surabhi Singh

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.