-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thanos Block UI do not show all blocks in v0.23.0 #4722
Comments
I am not sure why this happened. Probably it is still syncing block metadatas? Is this issue still happening? |
Hi. Yes it is still happening. These blocks are not displayed during several days continuous running of the pod. I think that it has something to do with new UI feature "#4462 UI: Highlighting blocks overlap in the Block UI.", because missing blocks are basically overlapping with already compacted blocks on higher lvl of compaction and only these blocks are missing from UI. But when I turn on this "highlighting" feature in UI, there is not shown ANY block. I wanted to look into the code to see if this feature was properly implemented, but I have not found the time for this. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
thanos, version 0.23.0 (branch: HEAD, revision: fe0d695)
build user: circleci@80970a8015b2
build date: 20210927-14:57:42
go version: go1.16.8
platform: linux/amd64
What happened:
Hi. I noticed, that new version of Thanos don't show all block from S3 in Block UI.
How you can see on image below. Left side is version v0.22.0 and right side is v0.23.0 (same blocks, same time-range). Also I noticed that ordering of block series is wierd in new version, but it's just a matter of opinions
https://imgur.com/Url1Ee3
How to reproduce it (as minimally and precisely as possible):
Only change version of image, all setting still same.
I'm running Thanos with this flags
Full logs to relevant components:
I think that log is useless, because it also remained the same, but here it is.
The text was updated successfully, but these errors were encountered: