Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3558

Allow to adjust the limit of nested objects in elasticsearch indexes of Optimize

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • L3 - Default
    • 3.1.0
    • None
    • backend
    • Not defined

    Description

      Context:

      The issue was raised that once a process instance has more than 10 000 activit instances/flow nodes Optimize will raise an exception since Elasticsearch won't allow Optimize to add more than 10 000 nested documents. In order to be able to fix the issue, the user should be able to adjust the limit.

      Error that occurs:

      [5]: index [optimize-process-instance_v4], type [_doc], id [], message [ElasticsearchException[Elasticsearch exception [type=mapper_parsing_exception, reason=The number of nested documents has exceeded the allowed limit of [10000]. This limit can be set by changing the [index.mapping.nested_objects.limit] index level setting.]]]
      

      AT:

      • the index.mapping.nested_objects.limit for all Optimize indexes in Elasticsearch can be configured in the Optimize configuration file
      • the new configuration is added to the documentation
      • the documenation of the config contains a hint that increasing this value might cause memory issue in Elasticsearch and/or slow down the search significantly

      Hint:
      Some possible options are:

      • the index.mapping.nested_objects.limit for all Optimize indexes in Elasticsearch can be configured in the Optimize configuration file
      • the documenation of the config contains a hint that increasing this value might cause memory issue in Elasticsearch and/or slow down the search significantly

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                johannes.heinemann Johannes
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce