-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
[CapMan visibility] Increase the default throttle/warning threshold for allocation policies #6189
Conversation
25ebac9
to
03a3fc7
Compare
DEFAULT_BYTES_THROTTLE_DIVIDER, | ||
), | ||
AllocationPolicyConfig( | ||
"threads_throttle_divider", | ||
"max threads divided by this number is the number of threads we use to execute queries for a throttled (project_id|organization_id, referrer)", | ||
int, | ||
DEFAULT_BYTES_THROTTLE_DIVIDER, | ||
DEFAULT_THREADS_THROTTLE_DIVIDER, |
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.
this fixes an existing bug
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.
let's update the test as well
policy.set_config_value("bytes_throttle_divider", 2) |
Test Failures Detected: Due to failing tests, we cannot provide coverage reports at this time. ❌ Failed Test Results:Completed 2518 tests with View the full list of failed testspytest
|
3fae75d
to
123a334
Compare
123a334
to
f17e139
Compare
IMO the title for this PR (and merge commit message, when it comes time for that) should be changed. This doesn't "get rid of sentry warnings" for throttled queries, it adjusts the threshold in the hopes of reducing the quantity of throttles and, downstream of that, the quantity of warnings we emit. The code change itself is fine, though. |
Allocation policies are our mechanism for doing traffic management for Snuba queries. Currently, we see a lot of warnings (Warning: Query from referrer ... is throttled) on Sentry Issues. This is because ~17% of queries to Snuba are throttled by capacity management/allocation policies. This is an overkill since we actually have a lot of Clickhouse capacity.
This PR increases the default throttle/warning threshold to be higher than half of the rejection threshold. I will also increase the thresholds in Snuba Admin.