Three replicas of one application against one PostgreSQL database, proving duplicate @Scheduled execution and then removing it with ShedLock: 24 executions where 8 were due, then 7 for 7 ticks. Also measured: @SchedulerLock without @EnableSchedulerLock does nothing and warns about nothing; spring.task.scheduling.pool.size=1 does not starve a fixedRate job but delays it and fires 35 of 40 executions in a burst; and a node whose clock is 40 seconds fast takes a live lock unless the provider uses usingDbTime().
9 lines
637 B
Plaintext
9 lines
637 B
Plaintext
[INFO] Running com.ankurm.scheduling.SingleSchedulerThreadTest
|
|
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.10 s -- in com.ankurm.scheduling.SingleSchedulerThreadTest
|
|
[INFO] Running com.ankurm.scheduling.LargerSchedulerPoolTest
|
|
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.422 s -- in com.ankurm.scheduling.LargerSchedulerPoolTest
|
|
[INFO] Running com.ankurm.scheduling.ClockSkewTest
|
|
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.964 s -- in com.ankurm.scheduling.ClockSkewTest
|
|
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
|
|
[INFO] BUILD SUCCESS
|