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

Dedicated ElasticsearchImportJobExecutor per ImportMediator/ImportService

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • L3 - Default
    • 2.4.0
    • None
    • backend
    • None

    Description

      AT:

      • each import flow should have a dedicated ElasticsearchImportJobExecutor instance (own queue and executor threads)

      Background:
      Currently one global ElasticsearchImportJobExecutor is shared between all import flows (completed process instance, running processInstance ...). This limits the throughput of the import to elasticsearch in the way that expensive write imports (user task, activityInstance & variables) tend to fill up the queue.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                sebastian.bathke Sebastian Bathke
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce