Skip to content

Conversation

@na--
Copy link
Contributor

@na-- na-- commented Sep 5, 2024

What this PR does:

Revert the grpc-go dependency to v1.65.0 to avoid a potential regression in the latest version. It's not yet clear whether the problem is indeed in grpc-go 1.66.0 or in how loki uses the library, but this allows downstream projects to also downgrade grpc-go without having to pin an older dskit version.

Potentially unrelated to that, it seems like v1.66.0 might have also introduced a performance regression too (grpc/grpc-go#7571), so that's another reason to downgrade.

Checklist

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

@trevorwhitney trevorwhitney merged commit 931a021 into main Sep 5, 2024
@trevorwhitney trevorwhitney deleted the ned/revert-grpc-upgrade branch September 5, 2024 22:18
krajorama added a commit to grafana/mimir that referenced this pull request Sep 6, 2024
Possible performance regression:
Ref: grafana/dskit#581

Also has breaking API changes for the experimental buffers.

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
krajorama added a commit to grafana/mimir that referenced this pull request Sep 6, 2024
* Vendor update mimir-prometheus at 53cf3fb8e7e3

* Add Close method to activity trackers
Followup to prometheus/prometheus#14064

* Pass logger to otlp FromMetrics
Followup to
grafana/mimir-prometheus#689

* Pin google GRPC to 1.65 for the time being
Possible performance regression:
Ref: grafana/dskit#581

Also has breaking API changes for the experimental buffers.

* Remove workaround in test
Follow up to:
prometheus/prometheus#14772

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
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