Repository navigation
1.5.1
1.5.1 fixes six faults reported against 1.5.0 and earlier: jobs that started late through the fallback, a second run of chain children stored by a version before 1.3.0, and claims that could be left InProgress or tried again for nothing. No database migration for EF Core, no change of the MongoDB collections, no new Redis key, no change of the public API or of a default.
Fixed
Jobs that started late
- A job added while the scheduler loop reads its next plan starts at its time (#78). The loop did not see the new job in that read and was not woken for it; the fallback started it, up to
FallbackIntervalChecker(30 seconds by default) late, and it endedDueDone. - EF Core or MongoDB with the Redis heartbeat: the release of a stopped node writes only that node's jobs (#90). It also wrote every waiting job no node held, which made the scheduler loop of the live nodes miss them; they started late through the fallback.
Redis as the job store
- An edit of a chain stored before 1.3.0 whose parent already ended runs no child (#152). Saving such a chain (
UpdateAsync, or the dashboard's edit) wrote its children as records of their own, and the fallback ran the ones the parent's outcome lets run, although 1.3.x had already run them. The edit now changes the parent's record only. - No pending entry is left on a job that ended (#57). A put-back that met a job ending at the same moment left one for good, and the fallback of cron occurrences never dropped the entry of an occurrence that had ended; each cost one claim attempt per fallback pass.
Claims
- A claimed job is put back later also when the store failed twice in a row during its claim (#155): the put-back of the row being claimed failed, then the put-back of the rows already won. It stayed
InProgressfor its node until the node restarted or its jobs were released. - A job whose slot came free as the application stopped does not start (#88). It would have run with a cancelled token and ended
Cancelled. No caller in the library reaches this path today.
Behaviour changes to check before upgrading
- Redis, chains stored before 1.3.0 whose parent already ended: an edit no longer runs their children, and what the edit carries for those children is not stored. To run them, delete the chain and add it again.
- Fewer jobs end
DueDone: jobs that started late through the fallback in the cases above start at their time.
Upgrade
From 1.5.0: no step. As with every release, an instance still on 1.5.0 behaves as 1.5.0 did: it still writes the children of such a chain when it is edited.
Known limits
Unchanged from 1.5.0; see its notes. The in-memory store's release of a stopped node still writes waiting jobs no node holds (#90 covers EF Core and MongoDB; nothing calls that release of the in-memory store in a running application).