Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5617

I can limit the number of existing jobs per batch

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • engine

      If a start a batch to migrate 4.000.000 process instances currently the batch seed job will try to create all 4.000.000 batch jobs even if they aren't processed yet. This might lead to a huge jobs table. Some operations fetch all jobs for a batch or count them. This might lead to performance issues.

      AT:

      • it exists a process engine configuration which limits the number of batch jobs which limits the number of jobs for a batch at any time
      • the seed job never creates more jobs than this configuration
      • (maybe) the seed job should than use a back off strategy to not to often poll the jobs count

        This is the controller panel for Smart Panels app

            [CAM-5617] I can limit the number of existing jobs per batch

            Sebastian Menski created issue -
            Sebastian Menski made changes -
            Link New: This issue is related to CAM-5557 [ CAM-5557 ]
            Sebastian Menski made changes -
            Description Original: If a start a batch to migrate 4.000.000 process instances currently the batch seed job will try to create all 4.000.000 batch jobs even if they aren't processed yet. This might lead to a huge jobs table. Some operations fetch all jobs for a batch or count them. This might lead to performance issues.

            AT:

            - it exists a process engine configuration which limits the number of batch jobs which limits the number of jobs for a batch at any time
            - the seed job never creates more jobs than this configuration             		New: If a start a batch to migrate 4.000.000 process instances currently the batch seed job will try to create all 4.000.000 batch jobs even if they aren't processed yet. This might lead to a huge jobs table. Some operations fetch all jobs for a batch or count them. This might lead to performance issues.

            AT:

            - it exists a process engine configuration which limits the number of batch jobs which limits the number of jobs for a batch at any time
            - the seed job never creates more jobs than this configuration
            - (maybe) the seed job should than use a back off strategy to not to often poll the jobs count
            Sebastian Menski made changes -
            Assignee New: Sebastian Menski [ sebastian.menski ]
            Sebastian Menski made changes -
            Rank New: Ranked higher
            Sebastian Menski made changes -
            Rank New: Ranked higher
            Daniel Meyer made changes -
            Fix Version/s Original: 7.5.0 [ 14091 ]
            Sebastian Menski made changes -
            Assignee Original: Sebastian Menski [ sebastian.menski ]
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 37963 ] New: Backup_camunda BPM [ 55816 ]
            Daniel Meyer made changes -
            Link New: This issue is related to CAM-10063 [ CAM-10063 ]

              Unassigned Unassigned
              sebastian.menski Sebastian Menski
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: