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

Dedicated ElasticsearchImportJobExecutor per ImportMediator/ImportService

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0
    • Component/s: backend
    • Labels:
      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: