-
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
[Compactor] Compactor has concurrent map writes / iterations and writes in v0.32.3 #6742
Comments
Hmm, we haven't changed anything specific on compactor in 0.32.3. We did bump objstore version tho: thanos-io/objstore@c042a6a...eb06103 cc: @fpetkovski |
Hi @saswatamcode, we went from 0.30.2 -> 0.32.3, so it could be any version in between that introduces the bug. To add some more context around the error:
(Btw the error "could not guess file size for multipart upload" is also a new thing introduced by the objstore, which is fixed in thanos-io/objstore#77.) Update: I think it's fixed in thanos-io/objstore#78, it's a race condition in the objstore so I suppose we can close this issue. |
While that log is old, I think something changed to trigger it and is addressed in thanos-io/objstore#77 For the concurrent map panic, I think the fix might just be thanos-io/objstore#78 |
Fwiw we don't see the panics with below config (but do see the "could not guess file size"),
|
v0.32.4 is now available with these fixes: https://github.com/thanos-io/thanos/releases/tag/v0.32.4 |
Thanos, Prometheus and Golang version used:
Object Storage Provider: In house Ceph cluster.
What happened:
The thanos compactor throws
fatal error: concurrent map iteration and map write
orfatal error: concurrent map writes
and error out.How to reproduce it (as minimally and precisely as possible):
TBD.
Full logs to relevant components:
fatal error: concurrent map writes: https://pastebin.com/raw/iWPVTQVV
fatal error: concurrent map iteration and map write: https://pastebin.com/raw/wrtHv76Q
Anything else we need to know:
Thanos compact args:
The text was updated successfully, but these errors were encountered: