fix: log retention throughput and widen the first-pass deadline - #24
Merged
Merged
Conversation
The 0.3.37 prune still dies mid-batch on the live router (one DELETE statement consuming the whole 5-minute budget). Until the pass reports per-table rows/seconds, the failure is unfalsifiable; this adds exactly that, plus a 15-minute budget for the first pass after an upgrade (a pass that dies just retries the same work an hour later, so the budget should fit a real backlog). No behavior change beyond the deadline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.3.37's index-driven batches still stall on the live router (one batch ate the 5-min budget at deleted=321). The pass now logs per-table rows/seconds/err and gets a 15-min first-pass budget; next field report will show actual batch throughput instead of a bare deadline error.