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 upMetrics corruption #388
Comments
grobie
added
bug
labels
Apr 11, 2014
This comment has been minimized.
This comment has been minimized.
|
Wow, this is internal LevelDB corruption. My first guess would be that there was an unclean shutdown of some sorts (but even then, unrecoverable corruption is uncommon). Did you happen to look at the logs whether Prometheus shut down cleanly? In any case, this doesn't seem like a bug caused by us storing wrong data in LevelDB. |
This comment has been minimized.
This comment has been minimized.
|
The log output including the previous shutdown info:
|
This comment has been minimized.
This comment has been minimized.
|
Closing this since the storage has been completely rewritten since. |
juliusv
closed this
Dec 10, 2014
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
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. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
grobie commentedApr 11, 2014
Steps:
Result:
Expected result:
Prometheus: 0.2.1
OS: debian wheezy 7.0 amd64
Log output:
@juliusv: I made a backup of the corrupted storage folder. Ping me for details.