Increase default value of rpc_client_connections_per_peer to 32
#16527
Conversation
This file contains 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
StephanDollberg
previously approved these changes
Feb 7, 2024
ballard26
force-pushed
the
inc-conn-per-peer
branch
from
054d34e
to
026323c
Compare
ballard26
changed the title
rpc_client_connections_per_peer to 24rpc_client_connections_per_peer to 32
StephanDollberg
approved these changes
Feb 7, 2024
|
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/44841#018d8589-f945-4956-88b7-8bbc543598eb |
|
/backport v23.3.x |
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.
This change aligns the default value of
rpc_client_connections_per_peerto what we set it to by default via k8s on Cloud clusters.Backports Required
Release Notes