-
Notifications
You must be signed in to change notification settings - Fork 917
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
Add lower priority for replication tasks #3870
Add lower priority for replication tasks #3870
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Should we use CallerTypePreemptable for archival queue?
Yeah, the plan is to use the new level/caller type for replication and all queues other than transfer/timer/visibility (@pdoerner Can you create a task for it). But that involves more changes: e.g right now task executable assumes all tasks are background, we need a ways to specify different caller type for different task categories. Same for the implementation on task loading. Given that the main motivation for this work is to resolve the issues we saw during namespace migration, I don't want to rush ^ changes for 1.20. |
What changed?
Added a new rate limiter priority for preemptable tasks which is lower than other background tasks (currently the lowest priority)
Applied this new priority to replication tasks
Why?
Replication tasks should have lower priority than other tasks because it can hog resources and impact active namespaces in a cell. This will allow us to throttle replication tasks independently from other background tasks.
How did you test it?
Update unit test
Potential risks
No risks
Is hotfix candidate?
No