Uploaded image for project: 'CloverETL'
  1. CloverETL
  2. CLO-2418

Optimize Execution history tree for huge number of jobs (10k+)

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: rel-3-5-0-M2
    • Fix Version/s: rel-4-0-0-M1
    • Component/s: Server
    • Security Level: Users (General product issues)
    • Branch:
    • QA Testing:
      GUI manual test

      Description

      Couple of issues with large number of jobs:

      1. When user runs a jobflow with 10k+ jobs and attempts to view that job in Execution history, CloverETL Server UI crashes with Java Exception Out of Heap Space or with GC overhead limit exceeded. Can we optimize UI to do the loads of information more selectively (I am not sure much gets loaded into memory and what is really needed)?
      2. Archivator should allow to filter the purge of Execution history also by JobName. Users often want to clean-up FINISHED_OK often running jobs but keep faild or sparsly running jobs in Execution history for a longer time.

        Attachments

          Activity

            People

            • Assignee:
              reichmanf Filip Reichman
              Reporter:
              ulrychj Jan Ulrych (Inactive)
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: