Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPanic #2115
Comments
This comment has been minimized.
This comment has been minimized.
|
My guess would be that in https://github.com/prometheus/prometheus/blob/c53b96b07da98e5d02be9364d137493a476ad89a/storage/local/series.go#L500 , the calculated cap became negative. The most likely reason for that is data corruption that lead to non-monotonic timestamps in the series. We should definitely guard against this by making sure the cap cannot become negative. @stamm To verify that this is a data corruption problem, could you start from a blank storage and see if the problem recurs? |
beorn7
referenced this issue
Oct 25, 2016
Merged
Add guard against non-monotonic samples in series #2116
This comment has been minimized.
This comment has been minimized.
|
It's working fine right now, without even restarted
|
brian-brazil
added
the
kind/bug
label
Oct 26, 2016
beorn7
closed this
Oct 26, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
stamm commentedOct 25, 2016
•
edited
What did you do?
Nothing really
What did you expect to see?
No errors
What did you see instead? Under which circumstances?
Go panic error:
Environment
Linux 3.10.0-327.10.1.el7.x86_64 x86_64
With some patches for etcd
prometheus, version 1.2.1 (branch: HEAD, revision: c53b96b07da98e5d02be9364d137493a476ad89a)
build user: root@****
build date: 20161011-14:42:12
go version: go1.6.2