You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d34f0ab
Browse filesBrowse the repository at this point in the historyBrowse files
docs(server)!: upgrade in order, keeping the scheduler running to drain runs
The server upgrade note no longer offers `scheduler = false`: the
scheduler loop launches queued runs and advances group runs, so with it
off nothing drains. It now gives the order to upgrade in and when to
resume schedules and sensors, and says that until a location has
published again a group's schedule or sensor stops the scheduler and a
job run that fails can't record its failure.
A test shows that failure: the worker's report that a job run failed is
refused, because deciding on a retry reads the snapshot's documents
before it checks for a retry policy, and the run stays running.
BREAKING CHANGE: a published job's `resolved_concurrency` is now
`{limit}`; its `source` field and the `ConcurrencySource` schema are
removed from the control API, and `sqb build --verbose` no longer names
the setting the concurrency came from. Control store migration 0004
removes the field from each stored job definition, but not from the
snapshot documents jobs were published in. Upgrade in this order:
1. Pause every schedule and sensor, and start no manual runs. Keep the
scheduler running.
2. Let queued and running runs finish, or cancel them.
3. Upgrade the server.
4. Upgrade and restart every location.
5. Once every location has published again, resume schedules and
sensors.
Until a location has published again, its job pages, group runs and ad
hoc runs fail, a group's schedule or sensor stops the scheduler, and a
job run that fails can't record its failure.
0 commit comments