Skip to content

v1.3.0-beta.3

Pre-release
Pre-release

Choose a tag to compare

@msx752 msx752 released this 11 Nov 17:59
54ea55f

A prerelease. It closes the known limit of 1.3.0-beta.2 for chains: the children without a time of their own now follow a parent outcome that was stored late. No public API change and no database schema change since 1.3.0-beta.2.

Fixed

  • Inline chain children run after a parent outcome that was stored late (#74). When a parent's final write failed and the scheduler stored it later, the parent's children without a time of their own stayed Idle, neither run nor skipped. They now follow the stored outcome: those it lets run are claimed from the store and run, those it does not let run are skipped with their descendants.
  • One rule on every store for claiming a chain child without a time by id (#99). Such a child is handed out by id only once its parent has ended with an outcome it runs on, and an InProgress child without a time never is. Redis refused every such claim before; EF Core, MongoDB and the in-memory store also allowed it for InProgress children. Nothing used this claim before this prerelease.
  • A job no longer starts before its time when another job is due in the same second (#117). The scheduler plans the jobs of one second together and started them all at the earliest of their times, so a time ticker or a delayed child could start up to one second early beside another time ticker or a cron occurrence. Each now starts at its own time. 1.3.0-beta.2 listed this as a known limit for cron occurrences only.

Behaviour changes to check before upgrading

  • A child that follows a late-stored outcome runs as a job of its own, not inside its parent's run: it takes its own concurrency slot and priority, and it ends Done also when the fallback had started its parent (which then ended DueDone). A child whose parent's outcome was stored at once runs inside the parent's run, as before.
  • Custom persistence providers are not fenced, so a lost outcome is not written again there and none of this applies.

Known limits in this prerelease

  • An inline chain child can still be left Idle and not run in these cases: its parent's outcome was stored only by the last write at the stop; its claim failed; the claimed child was put back; or its node was killed while it ran (#84). The log names the child in the first two cases. Nothing claims such a row later; add a new job to run it.
  • The start of an inline child by its parent's run is not a claim (#83): a child given a time while its parent runs can run twice.
  • At-least-once. A job whose process ended before its lost outcome was stored can run again after its rows are released.
  • Redis: a node that alone could not reach Redis for about two heartbeat TTLs, while the others could, has its running jobs released (#46).
  • Code-defined crons: replicas that start together can still create the same cron twice (#92).

What's Changed

  • Give the four stores one rule for claiming a child without a time by id by @msx752 in #113
  • Run inline chain children after a parent outcome that was stored late by @msx752 in #114
  • Add a container scenario for inline children after a late-stored outcome by @msx752 in #115
  • Give the late-loop cron scenario a pause Redis needs since #107 by @msx752 in #116
  • Do not start a job before its time when another job is due in the same second by @msx752 in #117
  • Make the early-start tests fail for the bug inside the whole suite, and add a container scenario by @msx752 in #118
  • Release 1.3.0-beta.3 by @msx752 in #119

Full Changelog: v1.3.0-beta.2...v1.3.0-beta.3