Skip to content

TaskExecutorRepeatTemplate should have option to not use throttleLimit #4734

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.

Sign up for GitHub

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

Jump to bottom
Closed
anupam-contaque opened this issue Dec 10, 2024 · 1 comment
Closed

TaskExecutorRepeatTemplate should have option to not use throttleLimit #4734

anupam-contaque opened this issue Dec 10, 2024 · 1 comment
Labels
status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details

Comments

@anupam-contaque
Copy link

Since throttling and related classes from org.springframework.batch.repeat.support are deprecated and will be removed, the TaskExecutorRepeatTemplate still uses the default throttle limit.
If the task executor submitted is already backed by thread pool then it doesn’t make sense to use the deprecated throttleLimit or even to create a custom RepeatOperations implementation for that.

There should be an option to skip the throttling entirely, along with the deprecated API. Clients cannot use the multi-threaded steps efficiently with only Spring Batch APIs.
@anupam-contaque anupam-contaque added status: waiting-for-triage Issues that we did not analyse yet type: feature labels Dec 10, 2024
@fmbenhassine
Copy link
Contributor

There will be a new approach to concurrency in v6, see #3950.

I am closing this ticket for same reason as #4531 (comment).

@fmbenhassine fmbenhassine closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2025
@fmbenhassine fmbenhassine added status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details and removed status: waiting-for-triage Issues that we did not analyse yet type: feature labels Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: declined Features that we don't intend to implement or Bug reports that are invalid or missing enough details
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fmbenhassine @anupam-contaque