-
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
receive: Query failure on Seg fault #3497
Comments
BTW I would vote for setting https://golang.org/pkg/runtime/debug/#SetPanicOnFault so we can recover on those. |
Root cause: Prometheus TSDB Checkpoint unmaps chunk even though we hold chunk querier against it. Most likely bug on TSDB side. Double checking still if we don't close prematurely on Thanos. |
Created: prometheus/prometheus#8217 |
not sure if it is the same issue, but I have SIGSEGV errors also in store 0.17. Attached logs. |
@arvidsnet nope, definitely different thing, let's create another issue (: Anyway, both will now on v0.17.1 cause query error NOT segment fault, so at list damage is smaller (: |
Created #3511 @arvidsnet help wanted to find the root cause! 🤗 |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
To investigate. |
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! 🤗 |
We are starting to experience this issue on regular basis now. Prometheus version is 0.40, Thanos version 0.29. Attaching logs following the panic that crashes many receivers at the same time. Seems to occur during head compaction. logs
|
From the duplicate issue discussion (I'll redirect that discussion to here) - possible culprit found by @philipgough #4306 (comment)
|
Looks like query uses ummaped piece of memory. Investigating.
The text was updated successfully, but these errors were encountered: