Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Number of requests to BATCH_JOB_EXECUTION_PARAMS depending on the number of previous executions #4499

Open
arno750 opened this issue Nov 25, 2023 · 0 comments
Labels
status: waiting-for-triage Issues that we did not analyse yet type: bug

Comments

@arno750
Copy link

arno750 commented Nov 25, 2023

Bug description
Between version 4.3.8 and 4.3.9, an increase in the number of requests on table BATCH_JOB_EXECUTION_PARAMS is observed. With each new batch execution, there is one an additional request.

Environment

  • Java 17
  • spring-boot-starter-parent 2.7.17
  • postgresql
  • spring-batch-core 4.3.9 (or 4.3.8 to show the difference)

Steps to reproduce
Run the same batch with allowStartIfComplete=true several times.
The number of SELECT is increasing by one each time.
spring-batch-demo.zip

Expected behavior
The number of SELECT should not be dependent on the number of previous executions.
With large history on table BATCH_JOB_EXECUTION_PARAMS, the number of SELECT is equally important. Considering this table has no index, there is a performance issue.

@arno750 arno750 added status: waiting-for-triage Issues that we did not analyse yet type: bug labels Nov 25, 2023
@arno750 arno750 changed the title Number of request to BATCH_JOB_EXECUTION_PARAMS depending on the number of previous execution Number of requests to BATCH_JOB_EXECUTION_PARAMS depending on the number of previous executions Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage Issues that we did not analyse yet type: bug
Projects
None yet
Development

No branches or pull requests

1 participant