Skip to content
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

Enable ingester to querier chunks streaming and ingester query request minimisation by default #6174

Merged
merged 6 commits into from
Nov 13, 2023

Conversation

charleskorn
Copy link
Contributor

@charleskorn charleskorn commented Oct 2, 2023

What this PR does

This PR enables two recently-introduced features by default, and marks them as no longer being experimental:

  • ingester to querier chunks streaming (store-gateway to querier chunks streaming will remain experimental for now)
  • ingester query request minimisation

Both of these features have been enabled in production at Grafana Labs for quite some time now, and we've had no issues with either of them.

Which issue(s) this PR fixes or relates to

(none)

Checklist

  • [n/a] Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

@charleskorn charleskorn marked this pull request as ready for review October 2, 2023 05:18
@charleskorn charleskorn requested review from a team as code owners October 2, 2023 05:18
@charleskorn charleskorn marked this pull request as draft October 2, 2023 06:29
@charleskorn
Copy link
Contributor Author

Putting this back to draft while I investigate an issue I've just noticed on an internal Grafana Labs cluster.

Copy link
Collaborator

@pracucci pracucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left you investigate the issue you've mentioned. If turns out it was a false positive, then I'm happy to mark it as stable and enable it by default. Good job!

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Contributor

@dimitarvdimitrov dimitarvdimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are there cases where this feature has to be disabled? I'm wondering if it's not a bad idea to enable them by default but then remove the flag after some time and always have the feature enabled? That will help keep the configuration surface of mimir smaller

Co-authored-by: Marco Pracucci <[email protected]>
@charleskorn
Copy link
Contributor Author

are there cases where this feature has to be disabled? I'm wondering if it's not a bad idea to enable them by default but then remove the flag after some time and always have the feature enabled? That will help keep the configuration surface of mimir smaller

Agree. There are no cases where you'd want to disable this based on our testing. I'd like to leave the flag there for a little while just in case there's an issue we haven't already run into, but I'd absolutely like to make streaming the default and remove the flag altogether if things go smoothly.

@dimitarvdimitrov
Copy link
Contributor

are there cases where this feature has to be disabled? I'm wondering if it's not a bad idea to enable them by default but then remove the flag after some time and always have the feature enabled? That will help keep the configuration surface of mimir smaller

Agree. There are no cases where you'd want to disable this based on our testing. I'd like to leave the flag there for a little while just in case there's an issue we haven't already run into, but I'd absolutely like to make streaming the default and remove the flag altogether if things go smoothly.

my comment was mostly about keeping the flag as experimental in this PR so that we can remove it without going through the deprecation process

@charleskorn
Copy link
Contributor Author

my comment was mostly about keeping the flag as experimental in this PR so that we can remove it without going through the deprecation process

Right, makes sense. Sounds good to me, I'll switch it back to experimental.

charleskorn and others added 2 commits October 10, 2023 14:35
…uests as experimental so we can remove them without deprecation in a later release
@charleskorn charleskorn marked this pull request as ready for review October 19, 2023 02:53
@charleskorn
Copy link
Contributor Author

#6346 fixed the issue I discovered and we've had no instances of the issue since rolling out that fix, so I believe this is good to go again.

Copy link
Contributor

@dimitarvdimitrov dimitarvdimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants