Open beatkind opened 1 month ago
Hi @beatkind
We strongly advise to upgrade your Loki installation to 3.2 and use TSDB as index type. boltdb-shipper
is deprecated.
It seems a cached boltdb file is the offender here:
"msg":"failed to open existing index file /var/loki/cache/loki_dis_index_19986/compactor-1726985323, removing the file and continuing without it to let the sync operation catch up"
You can try to empty the cache directory to see whether the problem persists.
Hi @beatkind We strongly advise to upgrade your Loki installation to 3.2 and use TSDB as index type.
boltdb-shipper
is deprecated.It seems a cached boltdb file is the offender here:
"msg":"failed to open existing index file /var/loki/cache/loki_dis_index_19986/compactor-1726985323, removing the file and continuing without it to let the sync operation catch up"
You can try to empty the cache directory to see whether the problem persists.
Hi @chaudum, thanks for the reply. Deleting the whole pvc (because it is most of the time easier) brings intermediate short-term improvement of the situation, until this happens again...
Describe the bug
We have a Loki setup inside GCP on GKE running. Deployed via the community helm chart and running in the distributed mode. We experience an interesting behaviour. When we query the last up to 24 hours, everything works as expected. But once I start querying a specific day in the past (23-09-2024) every thing stops working at all. Once I have done that, Loki is not responding to any query.
To Reproduce Steps to reproduce the behavior:
Expected behavior Get data back and dont stop working
Environment:
Screenshots, Promtail config, or terminal output
index-gateway-2.log index-gateway-3.log index-gateway-4.log