Details
-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Description
In https://github.com/camunda/camunda-optimize/pull/2830#discussion_r514181687, we added a check for the exceptions thrown by Elasticsearch to try to identify where the nested limit had been reached, in order to give users a hint as to how to solve it. However, the string we use to make this check is too broad and results in a lot of false positives (i.e. any nested exception also catches the check and the logged output is irrelevant and misleading). We should be more precise in how we determine whether the exception from elasticsearch actually is relating to the nested limit being reached.
The following support ticket contains reference to the original problem so could give a clue as to what other parts of the error message could be used: https://jira.camunda.com/browse/SUPPORT-7738