Skip to content

Commit 1ebb8c3

Browse files
quafffmbenhassine
authored andcommitted
Change start-limit to match example
playerSummarization is not started in Run 3.
1 parent 1e819a6 commit 1ebb8c3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

spring-batch-docs/asciidoc/step.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -432,7 +432,7 @@ The following example shows how to configure a job to have steps that can be res
432432
</tasklet>
433433
</step>
434434
<step id="playerSummarization">
435-
<tasklet start-limit="3">
435+
<tasklet start-limit="2">
436436
<chunk reader="playerSummarizationSource" writer="summaryWriter"
437437
commit-interval="10"/>
438438
</tasklet>
@@ -475,7 +475,7 @@ public Step gameLoad() {
475475
@Bean
476476
public Step playerSummarization() {
477477
return this.stepBuilderFactor.get("playerSummarization")
478-
.startLimit(3)
478+
.startLimit(2)
479479
.<String, String>chunk(10)
480480
.reader(playerSummarizationSource())
481481
.writer(summaryWriter())
@@ -497,7 +497,7 @@ every time in case extra files have been added since it last ran. It has
497497
'allow-start-if-complete' set to 'true' in order to always be started. (It is assumed
498498
that the database tables games are loaded into has a process indicator on it, to ensure
499499
new games can be properly found by the summarization step). The summarization step,
500-
which is the most important in the job, is configured to have a start limit of 3. This
500+
which is the most important in the job, is configured to have a start limit of 2. This
501501
is useful because if the step continually fails, a new exit code is returned to the
502502
operators that control job execution, and it can not start again until manual
503503
intervention has taken place.

0 commit comments

Comments
 (0)