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 upThe storage is now inconsistent. Restart Prometheus ASAP to initiate recovery #3029
Comments
This comment has been minimized.
This comment has been minimized.
|
Is this happening repeatedly after you have gone through crash recovery once? In general, there is a track record of subtle leveldb errors which are most likely due to corruptions on disk or bugs in leveldb. There is very little chance we will invest any work in investigating those as Prometheus 2 will not use LevelDB anymore. If the above issue goes away after going through crash recovery once, I'd take that as the appropriate work around for now. |
This comment has been minimized.
This comment has been minimized.
|
Nope it's only happened the once so I'll close this and wait for Prometheus 2. Thanks! |
adamdougal
closed this
Aug 7, 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. |
adamdougal commentedAug 7, 2017
What did you do?
Shut down prometheus
What did you expect to see?
Clean shut down
What did you see instead? Under which circumstances?
This following error log:
time="2017-08-04T13:12:17Z" level=error msg="The storage is now inconsistent. Restart Prometheus ASAP to initiate recovery." error="error in method hasArchivedMetric(cfe9908cdd5dcf2f): leveldb: closed" source="persistence.go:415"Environment
System information:
Linux 4.4.0-89-generic x86_64Prometheus version:
Logs:
Looks very similar to #2509