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

[NEW] Introduce a new client capability for throttling #872

Open
madolson opened this issue Aug 5, 2024 · 0 comments
Open

[NEW] Introduce a new client capability for throttling #872

madolson opened this issue Aug 5, 2024 · 0 comments
Labels
client-changes-needed Client changes are required for this feature enhancement New feature or request

Comments

@madolson
Copy link
Member

madolson commented Aug 5, 2024

With Valkey 8.0, we now have the ability for clients to indicate that they support a capability. One capability we discussed in Redis was the ability to shed load by sending an explicit throttle request. This is especially useful in caching cases, where the client would like to know they should go the backend database or API to fetch the data.

The main place we would like to send these requests is during a full-sync, where we may prefer to throttle incoming write requests instead of disconnecting replicas.

Related discussion on redis: redis/redis#12844.

@madolson madolson added the enhancement New feature or request label Aug 5, 2024
@madolson madolson added this to Roadmap Aug 5, 2024
@madolson madolson moved this to Idea in Roadmap Aug 5, 2024
@asafpamzn asafpamzn added the client-changes-needed Client changes are required for this feature label Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-changes-needed Client changes are required for this feature enhancement New feature or request
Projects
Status: Idea
Development

No branches or pull requests

2 participants