-
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
[minio storage] thanos store: compressed blocks stop working #552
Comments
Nice. Maybe it's |
no idea, all i can say is that thanos sidecar and thanos compact didn't have a problem writing to minio. |
What's the overall size of minio storage? It looks like minio bug rather than Thanos |
When i filed the bug the tsdb used something around 400MB. |
Looks like a duplicate of #271 (: This might be caused by sync inconsistency between store and compactor for example. |
Actually the reason might be similar to this: #146 We fetch fixed size series entries, so for series with an extremely large number of label pairs and chunks, we can have this problem. Looks like in this case Let's keep this in our mind, once we have more reports/see this more often we should investigate other options like:
|
Thanos, Prometheus and Golang version used
thanos build date: 20180925-07:41:17
go version: go1.10.3
prometheus: 2.4.2
local minio storage (version from 20180925)
What happened
As soon as compressed blocks did reach compaction level 6 and ~160MB Size, thanos gives errors like:
No datapoints found.
receive series: rpc error: code = Aborted desc = fetch series for block 01CR98G8ECSA44NMNGKSQ6EJ4T: preload series: invalid remaining size 65536, expected 103779
and the whole range for that block is missing in the graphs.
What you expected to happen
queries and plots working without any errors or gaps, just as it did one comaction level before.
The text was updated successfully, but these errors were encountered: