Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-489

PurgeBatchlet removes only executions. Instances are untouched which leads to OOM

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 1.1.0.Beta1, 1.3.4.Final
    • jberet-core
    • None

    Description

      https://github.com/jberet/jsr352/blob/master/jberet-core/src/main/java/org/jberet/repository/PurgeBatchlet.java removes only executions.
      Instances are untouched.

      When InMemoryRepository is used than it leads to OOM quite quickly.

      In our scenario 6 jobs per second fill up 750MB in less than 24 hours and ends by OOM even we run PurgeBatchlet every minute (all completed jobs).

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue JBERET-129 Implement ways to purge InMemoryRepository

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              weinanli Weinan Li
              lkrzyzan@redhat.com Libor Krzyžanek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: