-
Notifications
You must be signed in to change notification settings - Fork 456
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
pageserver: misrouted FSM key #10027
Labels
Comments
erikgrinaker
added
c/storage/pageserver
Component: storage: pageserver
t/bug
Issue Type: Bug
labels
Dec 5, 2024
This was referenced Dec 5, 2024
It's neon/pageserver/src/walingest.rs Lines 587 to 601 in dcb6295
I think we need the same shard filtering logic as for the corresponding visibility map code here: neon/pageserver/src/walingest.rs Lines 621 to 633 in dcb6295
|
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 6, 2024
## Problem FSM pages are managed like regular relation pages, and owned by a single shard. However, when truncating the FSM relation the last FSM page was zeroed out on all shards. This is unnecessary and potentially confusing. The superfluous keys will be removed during compactions, as they do not belong on these shards. Resolves #10027. ## Summary of changes Only zero out the truncated FSM page on the owning shard.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seen in #9943 (comment). An assertion shows that an FSM key was misrouted to shard 2 during
test_isolation
:The text was updated successfully, but these errors were encountered: