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 upCrash after Crash Recovery (len out of range) #2492
Comments
ichekrygin
changed the title
Crash after Crash Recovery
Crash after Crash Recovery (len out of range)
Mar 11, 2017
This comment has been minimized.
This comment has been minimized.
|
This is almost certainly triggered by data corruption crash recovery hasn't detected. In general, the unmarshaling code should be resilient against that and quarantine the series instead of crashing. This seems to hit yet another cornercase. |
beorn7
self-assigned this
Mar 13, 2017
beorn7
added
the
kind/bug
label
Mar 13, 2017
beorn7
added a commit
that referenced
this issue
Apr 4, 2017
beorn7
referenced this issue
Apr 4, 2017
Merged
storage: Check for negative values from varint decoding #2576
beorn7
closed this
Apr 4, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ichekrygin commentedMar 11, 2017
Restart Prometheus after abrupt termination
Prometheus starts, performs crash recovery, and starts serving requests
Prometheus starts, performs crash recovery, and crashes
Environment
System information:
Linux 4.7.3-coreos-r2 x86_64
Prometheus version:
prometheus, version 1.5.2 (branch: master, revision: bd1182d)
build user: root@1a01c5f
build date: 20170210-16:23:28
go version: go1.7.5
Alertmanager version:
N/A
Prometheus configuration file: