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.
raft: guard snapshot restore from deleting recently-seen instances #124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
raft: guard snapshot restore from deleting recently-seen instances #124
Changes from all commits
fa3392fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🔴 Critical | ⚡ Quick win
Fail closed when the instance reads fail.
Line 165 discards the error from
ReadRecentlySeenInstanceKeyMap. A query or resolution failure can leaverecentlySeenKeysempty or partial. The loop then treats every snapshot-absent key as stale and callsForgetInstance. Check both read errors before deleting any key. Return the restore error or skip the purge when either read fails.Suggested error handling
📝 Committable suggestion
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🔴 Critical | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 15414
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 27970
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 24071
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 10508
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 36906
🏁 Script executed:
Repository: ProxySQL/orchestrator
Length of output: 229
Make snapshot cleanup atomic with
last_seenupdates.ReadRecentlySeenInstanceKeyMapreadslast_seen, thenForgetInstancedeletes by key. A discovery write between these operations can be deleted. Add a DAO operation ingo/inst/instance_dao.gothat conditionally deletes by key and stale predicate in one SQLDELETE. UpdateforgetInstanceKeysanddiscardedKeysonly when the delete affects a row. Preserve currentNULL last_seenbehavior. Serialize or flush buffered discovery writes during restore. Add an interleaving test.🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.