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 477c7e2
Browse filesBrowse the repository at this point in the historyBrowse files
The v4.1.6 section only had the postinstall fix. Add the rest from the
commits in the release: the selector sample-count thresholds, the
scorer changes (crash loop, lock contention, catch-up, metrics and
tracing), and the revert of the single SubmitResults transaction from
v4.1.5, which caused deadlocks.
Copy file name to clipboardExpand all lines: CHANGES.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,21 @@
25
25
26
26
## v4.1.6
27
27
28
+
### Server
29
+
-**Selector sample-count thresholds**: The minimum sample counts for testing → active and candidate → testing promotions are derived from `interval_testing`. With `interval_testing` above about 45 minutes the fixed threshold couldn't be reached, which silently blocked every testing → active promotion. The default `interval_testing` is now 30 minutes (was 45).
30
+
-**Scorer catch-up**: While the scorer is behind, it skips redundant per-entry computation
31
+
-**Scorer metrics and tracing**: New `scorer_last_score_timestamp_seconds` and `scorer_last_batch_timestamp_seconds` gauges show how far behind the scorer is and whether monitors are submitting results; scorer SQL queries are traced with OpenTelemetry; the scorer metrics are documented in `scorer/README.md`
32
+
- Fix: The scorer no longer crashes and replays the same entry forever when a server has no recent monitor data, for example a server where every probe times out. Those entries are skipped and counted in `scorer_score_errors_skipped_total`.
33
+
- Fix: `SubmitResults` is back to one transaction per status; the single transaction added in v4.1.5 caused transaction deadlocks
34
+
- Fix: The scorer no longer holds row locks on `servers` for a whole batch, which made monitors' result submissions queue behind it. Servers are updated after the batch commits.
35
+
- Fix: Successful scorer batches no longer record an error span from a rollback after the commit
36
+
28
37
### Packaging
29
38
-**Postinstall systemd detection**: Skip `systemctl` calls when systemd isn't PID 1. The v4.1.2 check used `systemctl --version`, which succeeds in any container with `systemctl` installed; now check for `/run/systemd/system` instead.
0 commit comments