backend: add interpreted record replication message type #32
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
This is to be used by the safekeeper -> pageserver protocol.
erikgrinaker
approved these changes
Nov 18, 2024
VladLazar
deleted the
vlad/interpreted-wal-record-replication-support
branch
github-merge-queue bot
pushed a commit
to neondatabase/neon
that referenced
this pull request
Nov 25, 2024
…#9746) ## Problem For any given tenant shard, pageservers receive all of the tenant's WAL from the safekeeper. This soft-blocks us from using larger shard counts due to bandwidth concerns and CPU overhead of filtering out the records. ## Summary of changes This PR lifts the decoding and interpretation of WAL from the pageserver into the safekeeper. A customised PG replication protocol is used where instead of sending raw WAL, the safekeeper sends filtered, interpreted records. The receiver drives the protocol selection, so, on the pageserver side, usage of the new protocol is gated by a new pageserver config: `wal_receiver_protocol`. More granularly the changes are: 1. Optionally inject the protocol and shard identity into the arguments used for starting replication 2. On the safekeeper side, implement a new wal sending primitive which decodes and interprets records before sending them over 3. On the pageserver side, implement the ingestion of this new replication message type. It's very similar to what we already have for raw wal (minus decoding and interpreting). ## Notes * This PR currently uses my [branch of rust-postgres](https://github.com/neondatabase/rust-postgres/tree/vlad/interpreted-wal-record-replication-support) which includes the deserialization logic for the new replication message type. PR for that is open [here](neondatabase/rust-postgres#32). * This PR contains changes for both pageservers and safekeepers. It's safe to merge because the new protocol is disabled by default on the pageserver side. We can gradually start enabling it in subsequent releases. * CI tests are running on #9747 ## Links Related: #9336 Epic: #9329
conradludgate
pushed a commit
that referenced
this pull request
Nov 28, 2024
This is to be used by the safekeeper -> pageserver protocol.
conradludgate
pushed a commit
that referenced
this pull request
Dec 4, 2024
This is to be used by the safekeeper -> pageserver protocol.
conradludgate
pushed a commit
that referenced
this pull request
Dec 4, 2024
This is to be used by the safekeeper -> pageserver protocol.
conradludgate
pushed a commit
that referenced
this pull request
Jan 29, 2025
This is to be used by the safekeeper -> pageserver protocol.
conradludgate
pushed a commit
that referenced
this pull request
Jan 29, 2025
This is to be used by the safekeeper -> pageserver protocol.
conradludgate
pushed a commit
that referenced
this pull request
Jan 29, 2025
This is to be used by the safekeeper -> pageserver protocol.
arpad-m
pushed a commit
that referenced
this pull request
Jan 29, 2025
This is to be used by the safekeeper -> pageserver protocol.
arpad-m
pushed a commit
that referenced
this pull request
Jan 30, 2025
This is to be used by the safekeeper -> pageserver protocol.
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.
Add a new replication message type to support the interpreted safekeeper <-> pageserver protocol.
See also neondatabase/neon#9746