Skip to content
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

rpc: rm rangefeed RPC stream window special case #117545

Merged
merged 1 commit into from Jan 10, 2024

Conversation

pav-kv
Copy link
Collaborator

@pav-kv pav-kv commented Jan 9, 2024

The rangefeed stream window size tuning was introduced to mitigate OOM in rangefeeds caused by the excessive number of streams (one per Range). Since we now use mux rangefeeds (which multiplexes all the rangefeed traffic into a single stream), this setting is no longer needed, so this commit removes it.

Part of #108992

Release note (ops change): COCKROACH_RANGEFEED_RPC_INITIAL_WINDOW_SIZE env variable has been removed, and rangefeed connection now uses the same window size as other RPC connections.

The rangefeed stream window size tuning was introduced to mitigate OOM
in rangefeeds caused by the excessive number of streams (one per Range).
Since we now use mux rangefeeds (which multiplexes all the rangefeed
traffic into a single stream), this setting is no longer needed, so this
commit removes it.

Release note (ops change): COCKROACH_RANGEFEED_RPC_INITIAL_WINDOW_SIZE
env variable has been removed, and rangefeed connection now uses the
same window size as other RPC connections.
@pav-kv pav-kv requested a review from a team as a code owner January 9, 2024 15:58
Copy link

blathers-crl bot commented Jan 9, 2024

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@pav-kv
Copy link
Collaborator Author

pav-kv commented Jan 9, 2024

Is the non-mux code removed completely, or just disabled by default? If the code is still there, should we postpone removing this option, and remove it together with the code?

Copy link
Contributor

@erikgrinaker erikgrinaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but will defer to @miretskiy.

@erikgrinaker
Copy link
Contributor

Is the non-mux code removed completely, or just disabled by default?

The code is still there, to serve 23.2 clients in mixed-version clusters and for testing of the legacy endpoints. However, there is no way for a user to enable use of non-mux rangefeeds as an RPC client on a 24.1 node (the cluster settings and such are gone), so outbound RPC connections from a 24.1 node will never use non-mux rangefeeds.

@pav-kv
Copy link
Collaborator Author

pav-kv commented Jan 9, 2024

bors r=erikgrinaker,miretskiy

@craig
Copy link
Contributor

craig bot commented Jan 9, 2024

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Jan 9, 2024

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Jan 10, 2024

This PR was included in a batch that timed out, it will be automatically retried

@craig
Copy link
Contributor

craig bot commented Jan 10, 2024

Build succeeded:

@craig craig bot merged commit 05d1395 into cockroachdb:master Jan 10, 2024
10 checks passed
@pav-kv pav-kv deleted the rm-rangefeed-window-size branch January 10, 2024 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants