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
It occurs that the builder (and likely the compactor as well) delete blocks that are referenced in up-to-date metas in case there haven't been any changes to the block between different versions of the TSDB that has been used to build the block.
This is, because the new meta which is created from the block and the new TSDB is uploaded alongside the existing block that has already been uploaded before in a previous iteration.
However, since the planner also deletes the blocks referenced in out-of-date metas, the block is removed from storage, even though it's also references in the new meta.
This behaviour causes the gateway to not find these blocks in storage yielding to a low cache hit rate and lower filter rate.
Example logs from two tasks operating on the same keyspace:
Describe the bug
It occurs that the builder (and likely the compactor as well) delete blocks that are referenced in up-to-date metas in case there haven't been any changes to the block between different versions of the TSDB that has been used to build the block.
This is, because the new meta which is created from the block and the new TSDB is uploaded alongside the existing block that has already been uploaded before in a previous iteration.
However, since the planner also deletes the blocks referenced in out-of-date metas, the block is removed from storage, even though it's also references in the new meta.
This behaviour causes the gateway to not find these blocks in storage yielding to a low cache hit rate and lower filter rate.
Example logs from two tasks operating on the same keyspace:
Expected behavior
Blocks that are referenced in up-to-date metas are not deleted from storage.
The text was updated successfully, but these errors were encountered: