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.

Sign up for GitHub

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

Jump to bottom

rangefeed: use separate memory budgets for system and user tenant ranges #78977

Open
aliher1911 opened this issue Mar 29, 2022 · 0 comments
Open

rangefeed: use separate memory budgets for system and user tenant ranges #78977

aliher1911 opened this issue Mar 29, 2022 · 0 comments
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-kv KV Team

Comments

@aliher1911
Copy link
Contributor

aliher1911 commented Mar 29, 2022 •
edited by exalate-issue-sync bot
Loading

Is your feature request related to a problem? Please describe.
Currently tenants use single memory budget for all ranges. This could be problematic as changefeeds for user data could delay tenant system data if memory is scarce. Tenants should use separation between system and user range budgets similar to how it is used in system tenant.

Describe the solution you'd like
Tenant system ranges should have a smaller separate budget which should not be used by user ranges. It should also support dynamic system span configs (as added in #74555).
Mind that something needs to be done to handle asynchrony of config propagation. Existing fallbacks that declare all ranges as system is not good for rangefeeds as miscategorizing feed as system may compromise system feeds.

Jira issue: CRDB-14470

Epic CRDB-39959
@aliher1911 aliher1911 added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-kv-replication Relating to Raft, consensus, and coordination. T-kv-replication labels Mar 29, 2022
@aliher1911 aliher1911 mentioned this issue Mar 29, 2022
Open
@exalate-issue-sync exalate-issue-sync bot added T-kv KV Team and removed T-kv-replication labels Jun 28, 2024
@github-project-automation github-project-automation bot moved this to Incoming in KV Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-kv-replication Relating to Raft, consensus, and coordination. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-kv KV Team
Projects
No open projects
KV
Status: Incoming
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aliher1911