-
Notifications
You must be signed in to change notification settings - Fork 94
[Hold] Make retried Onyx writes idempotent on storage retry #792
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
Open
elirangoshen
wants to merge
4
commits into
Expensify:main
Choose a base branch
from
callstack-internal:elirangoshen/fix/retry-side-effects-idempotency
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+453
−45
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bfd6902
Make retried Onyx writes idempotent on storage retry
elirangoshen de62ae5
Regenerate API-INTERNAL.md for new write helpers
elirangoshen 11bc0a6
Restore cache state for evicted in-flight keys on retry
elirangoshen e70af5e
Fix lint: use `unknown[]` instead of `Array<unknown>`
elirangoshen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
When
Storage.multiSetfails with a capacity error,retryOperation()evicts an LRU key viaremove(), which immediately drops that key from cache and notifies subscribers before retrying. RetryingpersistMultiSetWrite(and similarlypersistCollectionWrite/persistMergedCollectionWrite) only re-attempts the storage write, so if the evicted key is part of the in-flight write, its cache value is never restored and subscribers keep the stale “removed” state even though storage eventually succeeds. This is a regression from the previous behavior where retries re-ran the orchestrator and re-applied cache updates.Useful? React with 👍 / 👎.
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.
Addressed in 11bc0a6.
Fix: each orchestrator (
multiSetWithRetry,setCollectionWithRetry,partialSetCollection,mergeCollectionWithPatches) now constructs arestoreEvictedKey(key)closure that re-applies its cache write + subscriber notification for a single in-flight key. The closure is passed via the write helper's params;retryOperationinvokes it afterremove(keyForRemoval)and before re-entering the write helper. No-op when the evicted key isn't part of this write (the typical case).mergeCollectionnuance: the closure snapshots the cache's post-merge state (not just the delta) so previously-merged-in fields survive when the eviction'scache.dropforces us to re-populate cache from scratch — otherwise we'd lose fields like{id: 1}when restoring after amergeCollection({key: {value: 'new'}})retry.Regression coverage: added 3 tests under
storage eviction— one per write helper — that mockStorage.multiSet/Storage.multiMergeto fail withdatabase or disk is fullonce on a setup where the LRU evictable key is the same key being written, and assert both cache + subscriber reflect the restored value (notundefined). All 3 fail without the lib changes (Received: undefined/ missing fields) and pass with them.459/459 tests pass; tsc and prettier clean.