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

Ensure that the Optimize import copes with concurrent process instance creation reliably

XMLWordPrintable

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

      Ensure that optimize imports data correctly when the engine is actively producing new data under considerable load.

      AT:

      • the following scenario is tested:
        • start the platform
        • start Elasticsearch
        • start the Optimize and with that automatically the import
        • generate/start 100 000 process instances while the import is running
        • compare the results with of the number of activity instances, process instance, process definitions, process definition xmls and variable instances are the same in the engine and in Optimize
      • I can read documentation about how to start this test (e.g. in a readme)
      • There is a jenkins job running nightly to execute this test.

      Hints:

      • The qa/import-performance-tests already contain the code to check if the entitiy count in Optimize and the engine are the same. Maybe we can extract the code from there.
      • the qa/data-generation module can be used to generate the 100 000 process instances with diagrams and variables.
      • in the .ci/jobs you will find the jenkins jobs. Here you can use the performance-large-dataset job as a template since it is already running nightly.

        This is the controller panel for Smart Panels app

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: