Failed to load chunk

Grafana Loki
1

The data has been deleted. How can we solve this issue? Is it possible to update the configuration and configure Grafana Loki to skip reading the deleted chunks

Failed to load log volume for this query

3 errors: rpc error: code = Unknown desc = failed to load chunk ‘fake/e80af0c9d9f05622/18fa33e9e55:18fa3ae5093:8c3f92ae’: failed to get s3 object: NoSuchKey: The specified key does not exist. status code: 404, request id: FJX28MR8BDG2AK0K, host id: esYGDNWgOJrTo+aXsaw2RA8QsN5D9M3SQzOXhCmTlazV6iMcNlm+AgGop1QKAGzttWlaqJ3IB4Q=; rpc error: code = Unknown desc = failed to load chunk ‘fake/e80af0c9d9f05622/18fa33e9e55:18fa3ac7bea:1a47e29’: failed to get s3 object: NoSuchKey: The specified key does not exist. status code: 404, request id: FJXB2AR49RX1GY79, host id: 57atOPkjpHRgqjXm3P9bafB7P64pUCCZVJvQvNrWjjIN9tMCM3k3yWY3JZimVbL9Ha48Cqw/cyk=; failed to load chunk ‘fake/e80af0c9d9f05622/18fa33e9e55:18fa3ae5093:8c3f92ae’: failed to get s3 object: NoSuchKey: The specified key does not exist. status code: 404, request id: WRPMZYVTNS8X38XS, host id: MQTnjc0biN0p/K2k6U2v4m2vW6nkptcfztQFUrPmtJioJT8/1gQcMaxvGOY5pDYWidRM7rNIKa4=

2

It depends. Were the chunks removed due to some sort of retention and all chunks past the same timeframe were removed as well? If so you could simply remove the index files past that timeframe as well. But if it’s random chunks then it’ll be much more difficult to track them down.

If it does not impact the functionality of your Loki cluster I’d be inclined to say ignore them and let the problematic index files get cycled out naturally by your retention policy (hopefully you have one).