You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error was gone and Loki was able to start after shared_store: s3 was commented out from BoltDB-Shipper and TSDB-Shipper config blocks.
To Reproduce
Steps to reproduce the behavior:
Add named_store block to the config.
Restart Loki to see it failing.
Comment out the shared_store line from storage congs.
Restart Loki without a problem
Expected behavior
I am not sure why commenting out shared_store: s3 helped, but from Loki code it seems like the bucketnames: line was ignored for some reason after introducing named stores. I am also not sure whether removing shared store line from TSDB and BoltDB-Shipper configs has any side effects, but the cluster seems to be working as usual for 2 days since the config change.
Environment:
Infrastructure: Microservice mode running Linux VMs with Ceph as S3 storage.
Was the common storage config removed after named_stores section is added?
If yes, setting shared_store to s3 is forcing the index shipper to init an object client with the config provided under common storage config (which is now empty)
Describe the bug
After adding named_store_configs block to the storage config Loki failed to start with the following error message:
This error was gone and Loki was able to start after
shared_store: s3
was commented out from BoltDB-Shipper and TSDB-Shipper config blocks.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I am not sure why commenting out
shared_store: s3
helped, but from Loki code it seems like thebucketnames:
line was ignored for some reason after introducing named stores. I am also not sure whether removing shared store line from TSDB and BoltDB-Shipper configs has any side effects, but the cluster seems to be working as usual for 2 days since the config change.Environment:
Configuration
Storage config before the change:
Storage config after the change:
The text was updated successfully, but these errors were encountered: