-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
feat(ingest-limits): Add ExceedsLimit implementation #15884
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.
Excellent work! A couple of questions, but otherwise LGTM!
pkg/limits/frontend/service.go
Outdated
for _, resp := range resps { | ||
sum += resp.Response.(*logproto.GetStreamUsageResponse).ActiveStreams | ||
if resp.Response == nil { |
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.
Is there a case where a resp.Response
can be nil when err
is also non-nil?
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.
No I guess it was just muscle memory to protect from nil rather than considering the code branches. This if-statement is obsolete.
pkg/limits/frontend/service.go
Outdated
// recorded | ||
for _, stream := range resp.Response.RecordedStreams { | ||
if !uniqueStreamHashes[stream.StreamHash] { | ||
uniqueStreamHashes[stream.StreamHash] = true |
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.
I find the code easier to read if we increment unique streams inside the if statement, instead of add the total and then subtract the duplicates. Is the latter much faster?
💻 Deploy preview deleted. |
What this PR does / why we need it:
Implements the
ExceedsLimit
GRPC request handler for requesting stream counts per tenant. The implementation currently is:Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR