Details
-
Bug
-
Status: Verified (View Workflow)
-
Major
-
Resolution: Done
-
None
Description
This is a followup issue for https://issues.redhat.com/browse/JBEAP-21993.
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
- clones
-
WFLY-14946 More efficient way of getting batch job executions by job name
-
- Closed
-
- follows up on
-
JBEAP-21993 [GSS](7.4.z) WFLY-14275 - Large job repository is blocking deployment
-
- Verified
-
- is blocked by
-
JBEAP-21777 [GSS](7.4.z) Upgrade jberet from 1.3.7.Final-redhat-00001 to 1.3.9.Final-redhat-00001
-
- Closed
-
- is cloned by
-
JBEAP-22201 (7.3.z) WFLY-14946 - More efficient way of getting batch job executions by job name
-
- Verified
-