Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3274 History Cleanup of Event Based Process data
  3. OPT-3890

Configurable cleanup batch size

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.1.0
    • None
    • backend
    • Not defined

      Context:
      In order to better control the process data cleanup which is batched from the side of Optimize now, the batch size should be configurable for cases where the request size of delete by id queries might exceed request limit sizes (thinking e.g. of aws elasticsearch deployments). Usually customers shouldn't need to adjust this, it's intended of a last resort in such cases.

      AT:

      • history cleanup batch size is configurable

      Hint:
      Docs will be amended with OPT-3891

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: