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 upExport a metric to tell if storage has become inconsistent #691
Comments
beorn7
self-assigned this
May 11, 2015
This comment has been minimized.
This comment has been minimized.
|
|
beorn7
referenced this issue
May 21, 2015
Merged
Add metrics to count inconsistencies and fp collisions. #714
juliusv
closed this
in
#714
May 21, 2015
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.
beorn7 commentedMay 11, 2015
Certain i/o errors (or unexpected errors, which are bugs) cause the storage layer to become inconsistent. In that case, an error message is logged and the storage is marked as dirty (so that a crash recovery will be performed after the next restart). This state should be exported as a metric so that monitoring can catch it.
@matthiasr here you are...