-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Consider making kv.dist_sender.concurrency_limit
cluster setting public in at least v24.3, possibly v24.1+
#135615
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
Comments
rmloveland
added
the
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
label
Nov 18, 2024
update: we should also do |
arulajmani
added a commit
to arulajmani/cockroach
that referenced
this issue
Nov 27, 2024
Closes cockroachdb#135615 Release note: None
arulajmani
added a commit
to arulajmani/cockroach
that referenced
this issue
Nov 27, 2024
While here, also do the same for kv.streamer.concurrency_limit. Closes cockroachdb#135615 Release note: None
arulajmani
added a commit
to arulajmani/cockroach
that referenced
this issue
Nov 28, 2024
Closes cockroachdb#135615 Release note: None
craig bot
pushed a commit
that referenced
this issue
Nov 28, 2024
136299: kvclient: make kv.dist_sender.concurrency_limit public r=kvoli a=arulajmani While here, also do the same for kv.streamer.concurrency_limit. Closes #135615 Release note: None Co-authored-by: Arul Ajmani <[email protected]>
@rmloveland, it turns out that these two settings take their default value from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
We are working on adding it to docs as a performance recommendation in some scenarios (see PR cockroachdb/docs#19096 for details)
via @sean- in discussion on the docs PR:
however, perhaps we would be willing to flip the setting to public on v24.1 and v24.2 even if we don't want to change the default
Jira issue: CRDB-44656
Epic CRDB-43580
The text was updated successfully, but these errors were encountered: