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
[OPT-2020] Dedicated ElasticsearchImportJobExecutor per ImportMediator/ImportService
Status | Original: Open [ 1 ] | New: In Development [ 10312 ] |
Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | New: Johannes [ johannes.heinemann ] |
Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
Assignee | Original: Johannes [ johannes.heinemann ] | New: Sebastian Bathke [ sebastian.bathke ] |
Status | Original: In Review [ 10212 ] | New: In Specification [ 10000 ] |
Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Specification [ 10000 ] | New: Done [ 10010 ] |
Remote Link | New: This issue links to "Page (camunda confluence)" [ 12804 ] |
Fix Version/s | New: 2.4.0 [ 15365 ] |
Labels | Original: current_release |
PM Priority | New: -1 |
PM Priority | Original: -1 |