Repository navigation
fix(gateway): reclaim orphan task pins on each node - #2235
Merged
Merged
Conversation
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
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.
Node-created task pins were absent from the gateway-only retention sweep, leaving 48 GiB of orphan inputs on one node.
Extend hourly retention to each node with the shared eligibility predicate. Inspect at most 32 pins and remove at most 8 per pass, rotating the cursor. Keep existing task directories, unarchived/replayable owners, parked work and unreadable provenance. Fence staging against admission/replay; purge outside the fence and preserve interrupted staging.
Validation: 42 focused Node 22 tests, five affected boundary suites, gateway typecheck and quality gates passed. Cancelled/done ownership regressions fail before the fix and pass after it. Private run
81fe8e6b-f3f3-4b14-808a-ee449bf0d067passed write-task, prepare and dispatch, then was cancelled and archived. Post-deploy proof will compare two nodes' pin inventories and verify zero active/parked pins removed.