Repository navigation
fix: recover orphaned ledger locks after host crashes - #55
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.
A freshly orphaned ledger lock previously timed out after 30 seconds, before its five-minute stale window, causing repeated restart failures (#53).
This change recovers locks owned by exited processes immediately, preserves live or indeterminate owners, and uses unique owner records inside a lock directory so competing reclaimers cannot delete a replacement owner's record. Legacy lock files remain supported. Clean startup skips write-lock acquisition; startup reconciliation failures are handled without discarding the ledger.
Validation: typecheck and build passed; all 517 tests passed, including a killed host and four independent writers recovering an orphan. This PR contains only the #53 recovery changes; #54 is handled separately.
Fixes #53