Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persist watermark updated prematurely #1059

Closed
beorn7 opened this Issue Sep 7, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@beorn7
Copy link
Member

beorn7 commented Sep 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.

@beorn7 beorn7 added the bug label Sep 7, 2015

@beorn7 beorn7 self-assigned this Sep 7, 2015

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Sep 7, 2015

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.

@beorn7

This comment has been minimized.

Copy link
Member Author

beorn7 commented Sep 7, 2015

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.

@lock

This comment has been minimized.

Copy link

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 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.
You can’t perform that action at this time.