Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1525 Ensure that the Optimize import copes with concurrent process instance creation reliably
  3. OPT-1547

Improve import fetch to cope with concurrent engine updates

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.3.0-alpha1, 2.3.0
    • None
    • backend
    • None

      Some process activity instances get missed when there is a high amount of data generated while the import is running concurrently and has progressed to the tip of the current time.
      In order to decrease the chance of missing concurrent writes in the engine the latest timestamp saved to continue in the next import cycle should get backed-off by a grace offset from the current time.

      Local Load-Testing with 10k-50k generated process instances showed that 2s appears to be a reasonable offset. The cost of this mitigation is reprocessing already imported entities and can be considered acceptable.

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: