@@ -432,7 +432,7 @@ The following example shows how to configure a job to have steps that can be res
432
432
</tasklet>
433
433
</step>
434
434
<step id="playerSummarization">
435
- <tasklet start-limit="3 ">
435
+ <tasklet start-limit="2 ">
436
436
<chunk reader="playerSummarizationSource" writer="summaryWriter"
437
437
commit-interval="10"/>
438
438
</tasklet>
@@ -475,7 +475,7 @@ public Step gameLoad() {
475
475
@Bean
476
476
public Step playerSummarization() {
477
477
return this.stepBuilderFactor.get("playerSummarization")
478
- .startLimit(3 )
478
+ .startLimit(2 )
479
479
.<String, String>chunk(10)
480
480
.reader(playerSummarizationSource())
481
481
.writer(summaryWriter())
@@ -497,7 +497,7 @@ every time in case extra files have been added since it last ran. It has
497
497
'allow-start-if-complete' set to 'true' in order to always be started. (It is assumed
498
498
that the database tables games are loaded into has a process indicator on it, to ensure
499
499
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
501
501
is useful because if the step continually fails, a new exit code is returned to the
502
502
operators that control job execution, and it can not start again until manual
503
503
intervention has taken place.
0 commit comments