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

The jsonnet doesn't seem suitable for multi-store configuration #11689

Open
umezawatakeshi opened this issue Jan 17, 2024 · 0 comments
Open

The jsonnet doesn't seem suitable for multi-store configuration #11689

umezawatakeshi opened this issue Jan 17, 2024 · 0 comments
Labels
component/compactor type/bug Somehing is not working as expected upgrade

Comments

@umezawatakeshi
Copy link

Describe the bug

The jsonnet always outputs .compactor.shared_store field in ConfigMap if boltdb_shipper and/or tsdb_shipper are used.
cf. https://github.com/grafana/loki/blob/v2.9.3/production/ksonnet/loki/shipper.libsonnet#L43

According to https://grafana.com/docs/loki/latest/setup/upgrade/#compactor-multi-store-support , .compactor.shared_store should not be configured for multi-store configuration to perform compaction on all stores.

I already have used Loki with multi-store configuration. Several days before, I noticed that the compaction hadn't been performed since I had upgraded Loki to 2.9.1 because the compactor tried to perform compaction on the latest period store but it only knew the way to perform compaction on the store in .compactor.shared_store.

To Reproduce

Expected behavior

I want a some option(s) for multi-store configuration.

Environment:

  • Deployment tool: jsonnet
  • Loki version: 2.9.1. But 2.9.3 seems to have the same behavior.

Screenshots, Promtail config, or terminal output
none

@JStickler JStickler added component/compactor type/bug Somehing is not working as expected labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/compactor type/bug Somehing is not working as expected upgrade
Projects
None yet
Development

No branches or pull requests

2 participants