-
Notifications
You must be signed in to change notification settings - Fork 512
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
Increase default Jaeger queue size for store-gateways and queriers #7068
Conversation
…eriers when using Helm
fcebfc7
to
e3cdb70
Compare
…elm / Jsonnet comparison
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, thanks
947c57e
to
5456a48
Compare
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 with one non-blocking comment.
@@ -61,6 +61,8 @@ | |||
), | |||
// Dynamically set GOMEMLIMIT based on memory request. | |||
GOMEMLIMIT: std.toString(std.floor($.util.siToBytes($.store_gateway_container.resources.requests.memory))), | |||
|
|||
JAEGER_REPORTER_MAX_QUEUE_SIZE: '1000', |
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.
Do we want to make this a configuration setting in jsonnet for parity with Helm?
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.
Marco suggested not doing that in https://github.com/grafana/mimir/pull/6764/files#diff-f3070297971f928d50b986208d8f23344d5c0a1d37f2c1422eed86feea6bb31a, so I'm following the pattern established there. I'd be happy either way.
I went for a different approach in Helm because I believe it's a harder (or even impossible) to extend the default value of something, so it'd be tricky for someone to extend our default set of environment variables that includes JAEGER_REPORTER_MAX_QUEUE_SIZE
with additional variables. Might be wrong though.
… size for all components configurable in Helm chart (#7086) * Set JAEGER_REPORTER_MAX_QUEUE_SIZE for write and backend containers deployed by Jsonnet. * Upstream default values of JAEGER_REPORTER_MAX_QUEUE_SIZE used for query-frontends, ingesters and rulers at Grafana Labs * Add support for setting Jaeger reporter max queue size to Helm chart * Update default values in Helm chart for ruler, ingester and query-frontends * Add changelog entries, and fix location of Helm chart changelog entry added in #7068.
What this PR does
This PR upstreams a change we've made internally at Grafana Labs which reduces the number of trace spans dropped due to the Jaeger client queue becoming full.
It increases the value of Jaeger's queue size for store-gateways and queriers when using Helm and Jsonnet.
Note that the increase for queriers when using Jsonnet was already applied in https://github.com/grafana/mimir/pull/6764/files#diff-b51f5403fbd4f68fb4ad925c7fdd104a50c4165085b19f75b54405472f74b8f0.
Note to reviewers: if the pattern of adding a
jaegerReporterMaxQueueSize
Helm value for each component looks good, I'll follow up this PR with another to add this for all components.Which issue(s) this PR fixes or relates to
(none)
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.