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 upPersist watermark updated prematurely #1059
Comments
beorn7
added
the
bug
label
Sep 7, 2015
beorn7
self-assigned this
Sep 7, 2015
This comment has been minimized.
This comment has been minimized.
|
Regarding partial appends, we currently error when we see a file with wrong length (not a multiple of the expected chunk size), but we don't attempt to ever repair it. |
This comment has been minimized.
This comment has been minimized.
|
That might be because in that case, we can't be sure what happened anyway. But I think we should do something when encountering an error appending to a file. Whatever, I will investigate. |
beorn7
referenced this issue
Mar 3, 2016
Merged
Quarantine series upon problem writing to the series file #1453
beorn7
closed this
in
fc7de53
Mar 17, 2016
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 commentedSep 7, 2015
In https://github.com/prometheus/prometheus/blob/master/storage/local/storage.go#L1008 , the call to series.chunksToPersist() already updates the persist watermark. However, in the following, the series file write may fail (in case of a rewrite it will be all or nothing, in case of appending it might even partially fail), in which case the persist watermark needed to be adjusted (or better set to the appropriate value after successful write of the new series file).
Also, consider how to recover from a partial append.