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 upCompatible Versions. Prometheus DB will not be removed. #4502
Comments
This comment has been minimized.
This comment has been minimized.
|
Thanks for your report. It looks as if this is actually a question about usage and not development. To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future. |
simonpasquier
closed this
Sep 6, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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. |
anumercian commentedAug 15, 2018
•
edited by simonpasquier
Hello, I was using the 1.8 version of Prometheus, I used to encounter the issue of corrupted data and I used storage.local.dirty=true flag to resolve this problem. After upgrading to version 2.3, this flag is no more supported, but I sometimes still get the corrupt data issue. What could I do in version 2.3 to avoid this problem? Attached are the logs. Could this be happening because of failed upgrade?
Use case. Why is this important?
Prometheus fails to start
journalctl -u prometheus -af