Dedicated ElasticsearchImportJobExecutor per ImportMediator/ImportService

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.4.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      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.

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: