-
Notifications
You must be signed in to change notification settings - Fork 25k
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
StackOverflowError when parsing deeply nested mappings #14370
Comments
@ppf2 it sounds reasonable to me to have a sensible default to the limit. Do you know how deep these mappings went? Could we reasonably pick "100" as the limit for nesting? |
@dakrone Will send you a sample offline. I think we can choose a default, and also expose this as a configurable setting? |
100 seems crazy high to me. |
@ppf2 We don't need a sample, I was just curious the number of levels it went down (not the actual mapping) |
@dakrone In this case, easily > 500 levels 😮 |
Closing in favour of #11511 |
Have a scenario where ES is throwing a StackOverflowError when the data node receives a cluster state published by the master. It is failing when parsing the mappings.
In this particular case, there is an explosion in mapped fields due to dynamically created fields where a single field ends up having many many levels of nesting (recursion). As a result, StackOverflowError shows up whenever the mappings has to be parsed so that the nodes cannot process the updates.
It will probably be helpful if we have a sensible default to limit the number of depth levels for a field, etc..
The text was updated successfully, but these errors were encountered: