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

chore: Disable bloom filtering for bounded sharding strategy #14272

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

chaudum
Copy link
Contributor

@chaudum chaudum commented Sep 25, 2024

What this PR does / why we need it:

This commit temporarily disables bloom filtering chunk refs in the GetShards() call on the index gateway when using the bounded sharding strategy.

This will result in chunks only being filtered once by the bloom gateway, reducing the amount of checks that need to be done on the bloom filters for a single request.

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Documentation added
  • Tests updated
  • Title matches the required conventional commits format, see here
    • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
  • Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
  • For Helm chart changes bump the Helm chart version in production/helm/loki/Chart.yaml and update production/helm/loki/CHANGELOG.md and production/helm/loki/README.md. Example PR
  • If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR

This commit temporarily disables bloom filtering chunk refs in the
GetShards() call on the index gateway when using the `bounded` sharding
strategy, because it adds a significant amount of additional load on the
bloom gateways.

Signed-off-by: Christian Haudum <[email protected]>
@chaudum chaudum force-pushed the chaudum/disable-bloom-filters-get-shards branch from d952127 to 14070bc Compare September 26, 2024 06:11
@chaudum chaudum marked this pull request as ready for review September 26, 2024 06:11
@chaudum chaudum requested a review from a team as a code owner September 26, 2024 06:11
Copy link
Contributor

@ashwanthgoli ashwanthgoli left a comment

Choose a reason for hiding this comment

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

LGTM
nit: would it make sense to make this configurable?

@chaudum
Copy link
Contributor Author

chaudum commented Sep 26, 2024

LGTM nit: would it make sense to make this configurable?

I thought about it, but I did not want to introduce yet another setting.

@chaudum chaudum merged commit 6143a54 into main Sep 26, 2024
61 checks passed
@chaudum chaudum deleted the chaudum/disable-bloom-filters-get-shards branch September 26, 2024 06:35
LashaJini pushed a commit to LashaJini/loki that referenced this pull request Sep 26, 2024
…#14272)

This commit temporarily disables bloom filtering chunk refs in the `GetShards()` call on the index gateway when using the `bounded` sharding strategy.

This will result in chunks only being filtered once by the bloom gateway, reducing the amount of checks that need to be done on the bloom filters for a single request.Signed-off-by: Christian Haudum <[email protected]>
jeschkies pushed a commit to jeschkies/loki that referenced this pull request Oct 1, 2024
…#14272)

This commit temporarily disables bloom filtering chunk refs in the `GetShards()` call on the index gateway when using the `bounded` sharding strategy.

This will result in chunks only being filtered once by the bloom gateway, reducing the amount of checks that need to be done on the bloom filters for a single request.Signed-off-by: Christian Haudum <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants