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

Revert map pooling #11584

Closed
wants to merge 7 commits into from
Closed

Revert map pooling #11584

wants to merge 7 commits into from

Conversation

cstyan
Copy link
Contributor

@cstyan cstyan commented Jan 4, 2024

backport the revert

chaudum and others added 7 commits January 2, 2024 18:06
The `Ref` of `MetaRef` and `BlockRef` do have start and end timestamps,
which are of type `int64`.
This however, can lead to the problem that different components might
use different precisions (`s`, `ms`, `ns`) for these timestamps.

This PR changes the current implementation of the bloom shipper to use
`ms` precision timestamps (using `model.Time`) instead of `s`, to match
the behaviour that we have to encode ChunkRefs to object store keys.

Signed-off-by: Christian Haudum <[email protected]>
Also updated the Docker image to match the latest version

Signed-off-by: Christian Haudum <[email protected]>
It is useful for implementations of Tee to also know the tenant who sent
the logs. This PR adds tenant to the tee interface.
…11539)

**What this PR does / why we need it**:
Add support for caching metadata queries (both series and labels).
caching happens after splitting similar to other types of queries.

This pr adds the following configs to enable them.
```
cache_series_results: true|false (default false)
cache_label_results: true|false (default false)
```
And the cache backend for them can be configured using
`series_results_cache` and `label_results_cache` blocks under the
`query_range` section.

Currently the split interval for metadata queries is fixed and defaults
to 24h, this pr makes it configurable by introducing
`split_metadata_queries_by_interval`

**Which issue(s) this PR fixes**:
Fixes #<issue number>

**Special notes for your reviewer**:

**Checklist**
- [x] Reviewed the
[`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md)
guide (**required**)
- [x] Documentation added
- [x] Tests updated
- [ ] `CHANGELOG.md` updated
- [ ] If the change is worth mentioning in the release notes, add
`add-to-release-notes` label
- [ ] 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](d10549e)
- [ ] 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](0d4416a)

---------

Signed-off-by: Kaviraj <[email protected]>
Co-authored-by: Ashwanth Goli <[email protected]>
Signed-off-by: Callum Styan <[email protected]>
@cstyan cstyan requested a review from a team as a code owner January 4, 2024 21:10
@github-actions github-actions bot added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Jan 4, 2024
@cstyan cstyan closed this Jan 4, 2024
Copy link
Contributor

github-actions bot commented Jan 4, 2024

Trivy scan found the following vulnerabilities:

  • HIGH, Target: docker.io/grafana/loki:k183-76bf505 (alpine 3.18.4), Type: alpine openssl: Incorrect cipher key and IV length processing in libcrypto3 v3.1.3-r0. Fixed in v3.1.4-r0
  • HIGH, Target: docker.io/grafana/loki:k183-76bf505 (alpine 3.18.4), Type: alpine openssl: Incorrect cipher key and IV length processing in libssl3 v3.1.3-r0. Fixed in v3.1.4-r0
    \nTo see more details on these vulnerabilities, and how/where to fix them, please run docker build -t grafana/loki:k183-76bf505 -f cmd/loki/Dockerfile .
    trivy i grafana/loki:k183-76bf505 on your branch. If these were not introduced by your PR, please considering fixing them in via a subsequent PR. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XXL type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants