Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14946

More efficient way of getting batch job executions by job name

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 25.0.0.Beta1, 25.0.0.Final
    • 24.0.0.Final
    • Batch
    • None

    Description

      Currently BatchJobExecutionResource.refreshChildren() method first loads all job instances by job name, and iterate through job instances to get job executions for each job instance. This is not efficient and has resulted in too many db queries, and sometimes high memory consumption and frequent GC activities.

      A more efficient way is to be able to retrieve all job executions belonging to a job in one operation.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-14966 Switch to Jakarta artifacts in batch subsystem and tests

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-22172 (7.4.z) More efficient way of getting batch job executions by job name

          • 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.
          • Verified
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBERET-506 Support retrieving job executions by job name

          • 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
          relates to

          Feature Request - Feature requests from customers and/or users WFLY-7418 Batch deployments with a large number of executed jobs can lock up or slow down the web console

          • 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.
          • Pull Request Sent

          Bug - A problem that impairs or prevents the functions of the product. WFLY-14275 Large job repository is blocking deployment

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-14952 Upgrade jberet-core from 1.3.8.Final to 1.3.9.Final

          • 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.
          • Closed

          Activity

            People

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: