Now throttlerLimit() is deprecated everywhere, providing a ThrottlerRepeatOperations could be convenient

[nightswimmings]

As per the note "@deprecated with no replacement since 5.0, scheduled for removal in 6.0. Use a custom {@link RepeatOperations} implementation (based on a {@link TaskExecutor} with a bounded task queue) and set it on the step with {@link #stepOperations(RepeatOperations)}.", I think it would be convenient to have some built-in replacement.

IMO this is pertinent because:

• It saves a significant effort to anyone that wants to upgrade
• I believe it is really something quite intrinsical to an expected Batch API
• It implies one of the most sensible ways of dealing with low-level stuff, concurrency and synchronization, and you all are much more aware of how things work in behind

My 2 cents, but thanks either way!

[Mom0aut]

Could someone provide an real example of how i can set the "old" throttleLimit with the "new" RepeatOperations.

Thanks!

[rmaheshk]

The document is unclear on how to use custom RepeatOperation to replace the deprecation of throttleLimit however, I have implemented as follows after going through few documentation but still no use

 @Bean
    public RepeatOperations createRepeatOperations() {
        TaskExecutorRepeatTemplate repeatOperations = new TaskExecutorRepeatTemplate();
        repeatOperations.setTaskExecutor(taskExecutor());
        return repeatOperations;
    }

and use the createRepeatOperations() through AbstractTaskletStepBuilder.stepOperation()

[NaitYoussef]

The solution you provided @rmaheshk won't work since you're using TaskExecutorRepeatTemplate which it self uses the deprecated method. You should implement your own custom RepeatOperations for it to work.
Check this post it says the same thing #4389 (comment)

[advaidg]

@NaitYoussef Any samples?
@rmaheshk - If you were able to fix this please share the details

[RT-1904129]

Hi @NaitYoussef ,@rmaheshk
Can you give me some Tips or examples on how to implement this ???

[overlinden]

@NaitYoussef @rmaheshk @RT-1904129

I would appreciate to have some valuable hints how to get a functional equivialent to the throttleLimit in the step configuration.
I have a computation based job and it is a waste of capacity to use 4 cores only instead of all available ones.

I could implement a workaround to use chunkSize(1) from spring batch perspective and modify the item reader / processor / writer to process a List of items at once. Within the item processor I use a Fork Join Pool implementation for parallelization.

I know that this is not a perfect solution but wasting a lot of CPU capacities is not feasible for me; the job would run for days instead of a couple of hours.

[harshalh10]

Hi @fmbenhassine, If you could assist us implementing in custom RepeatOperations it would be a great help.

[fmbenhassine]

There is no replacement for that API because the concept of a parallel iteration is flawed by design (see "Concurrency model" in #3950). I saw no reason to invest time in providing a temporary replacement for a flawed approach (ie providing another RepeatOperations implementation) that is going to last a short period of time.

The new approach to concurrency is coming in the next major release v6 which is planned for later this year. In the meantime, and if it were up to me, I would continue using the deprecated API until the official replacement is provided by Spring Batch.

I am closing this issue for now, keep tuned for #3950 !