Repository navigation
docs(wiki): document behavior when storage is unavailable (#633) - #643
Merged
Merged
Conversation
- delivery-guarantees: 'When storage is unavailable' section (dispatcher, heartbeats, orphan watcher, enqueue, HeartbeatTimeout guidance) - troubleshooting: database outage entry with the real log messages - how-we-test: an outage is not covered by provider tests - storage pages link to the new section
|
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.
Summary
Documents what the code does when the database is down or fails over: dispatcher fetch, job and node heartbeats, orphan watcher, enqueue, and
HeartbeatTimeoutguidance. Only facts proven by the code are written; each was checked at its source location. Behavior that is suspected to be a defect is not described as behavior and is tracked separately.Type of change
Verification Checklist
--strict: 0 driftmkdocs build --strictpassesCHANGELOG.mdupdated under[Unreleased]src/or tests changedNot covered by this PR
No test cuts a real database connection, so the page says the behavior comes from code reading and mock-based unit tests (listed in how-we-test). Open points: #640 (dispatcher loop ends if the runtime settings read throws), #641 (failure commit has no retry), #642 (candidate risks to reproduce).
Closes #633