Thanos store request fails trying to access deleted blocks #6445
Replies: 1 comment
-
After upgrade to latest Thanos version, issue has gone |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
We are using Thanos and S3 storage for long time retention of the data. A compactor is running for downsampling and retention purpose. Everything works fine, but after a while (~12h or more) we are encountering errors on request trying to access deleted block of data.
Errors comes with this message on store logs :
Referenced block 01H2T6K8X7S6TXNJ9MD786ZDXP is no longer existing in the bucket
But it is still referenced on the local store cache :
/store/meta-syncer/01H2T6K8X7S6TXNJ9MD786ZDXP sitll present with meta.json file
From compator logs, the block is deleted :
The main store settings includes the following parameters :
--ignore-deletion-marks-delay=15m
--sync-block-duration=30m \
type: IN-MEMORY
chunk_object_attrs_ttl: 30m
chunk_subrange_ttl: 30m
metafile_exists_ttl: 30m
metafile_doesnt_exist_ttl: 15m
metafile_content_ttl: 30m
In the store log file some messages "dropped outdated block" are present, but after a while there is no more message regarding dropped block in the log.
5 hours has elapsed between the deletion of the block by the compactor and the error encountered in the store query.
Any idea on which parameter could help in clearing more frequently the outdated block in the cache?
How can I check if the Block Synchronization is still running ?
Thanos version : 0.30.1
Beta Was this translation helpful? Give feedback.
All reactions