-
Notifications
You must be signed in to change notification settings - Fork 543
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
2.14 release notes #9406
2.14 release notes #9406
Conversation
7dc4f1b
to
eba6db6
Compare
Signed-off-by: Vladimir Varankin <[email protected]>
eba6db6
to
2f179f6
Compare
|
||
The minimal supported version of Go is updated to 1.22. | ||
|
||
The streaming of the chunks from store-gateways to queriers is enabled by default. |
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.
Can we "sell" this somehow? What does this bring to users?
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.
Added additional note about the feature
due to the compactor being out of disk. A new related alert `MimirCompactorHasRunOutOfDiskSpace` and it's runbook are added. | ||
|
||
Incoming OTLP requests were previously size-limited with the distributor's `-distributor.max-recv-msg-size` configuration. | ||
Distributor has a new `-distributor.max-otlp-request-size` configuration for limiting OTLP requests. The default value is set to limit request to 100 MiB. |
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.
We run with 20MB limit internally, we should change the default.
Incoming OTLP requests were previously size-limited with the distributor's `-distributor.max-recv-msg-size` configuration. | ||
Distributor has a new `-distributor.max-otlp-request-size` configuration for limiting OTLP requests. The default value is set to limit request to 100 MiB. | ||
|
||
Distributor now replies with `Retry-After` header on retryable errors. The feature is controlled by the `-distributor.retry-after-header.enabled` configuration, |
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 feature is not new (it was already mentioned in Mimir 2.11 release notes). I don't think this needs a call out.
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 think we now just enable it by default. Maybe we can mention what this means for users? It's that recovering from a Mimir outage should be easier now as the prometheus instances should respect Retry-After. ideally we can also mention how they should configure prometheus to respect retry-after headers. I'm not sure what the impact is for OTEL users
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.
Added additional note about the feature.
Co-authored-by: Taylor C <[email protected]>
Signed-off-by: Vladimir Varankin <[email protected]>
🆙 Hey, all. Thank you for the feedback. I worked through all comments, and the PR is ready for another round of review |
Signed-off-by: Vladimir Varankin <[email protected]>
5083e32
to
4ba3dd3
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. (suggested some wording changes, but feel free to ignore)
Co-authored-by: Peter Štibraný <[email protected]>
* draft 2.14 release notes Signed-off-by: Vladimir Varankin <[email protected]> * Apply suggestions from code review Co-authored-by: Taylor C <[email protected]> * update release-notes Signed-off-by: Vladimir Varankin <[email protected]> * note on deprecating redis Signed-off-by: Vladimir Varankin <[email protected]> * Apply suggestions from code review Co-authored-by: Peter Štibraný <[email protected]> --------- Signed-off-by: Vladimir Varankin <[email protected]> Co-authored-by: Taylor C <[email protected]> Co-authored-by: Peter Štibraný <[email protected]> (cherry picked from commit b1cce37)
* draft 2.14 release notes Signed-off-by: Vladimir Varankin <[email protected]> * Apply suggestions from code review Co-authored-by: Taylor C <[email protected]> * update release-notes Signed-off-by: Vladimir Varankin <[email protected]> * note on deprecating redis Signed-off-by: Vladimir Varankin <[email protected]> * Apply suggestions from code review Co-authored-by: Peter Štibraný <[email protected]> --------- Signed-off-by: Vladimir Varankin <[email protected]> Co-authored-by: Taylor C <[email protected]> Co-authored-by: Peter Štibraný <[email protected]> (cherry picked from commit b1cce37) Co-authored-by: Vladimir Varankin <[email protected]>
What this PR does
This is a draft PR that I'll populate with the 2.14 release notes.These are the release notes for the 2.14 release.
Which issue(s) this PR fixes or relates to
Relates to #9382
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.