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

tsdb: Isolation for writes #5873

Closed
gouthamve opened this issue Jan 16, 2018 · 4 comments · May be fixed by prometheus-junkyard/tsdb#306
Closed

tsdb: Isolation for writes #5873

gouthamve opened this issue Jan 16, 2018 · 4 comments · May be fixed by prometheus-junkyard/tsdb#306

Comments

@gouthamve
Copy link
Member

Currently, when we call app.Commit(), we go ahead and start adding samples to the database. But now if there is a concurrent reader that is reading data, it might read some samples from the commit but not all.

This causes issues in Prometheus and has been known to make histograms falter: #1169

This PR is an attempt to fix it: prometheus-junkyard/tsdb#105

@fabxc
Copy link
Contributor

fabxc commented Jan 16, 2018 via email

@brian-brazil
Copy link
Contributor

Isolation is a fairly core thing for a database, I'd be surprised if it didn't require a similar level of changes as what I proposed.

@fabxc
Copy link
Contributor

fabxc commented Jan 16, 2018 via email

@bwplotka bwplotka transferred this issue from prometheus-junkyard/tsdb Aug 13, 2019
@bwplotka bwplotka changed the title Isolation for writes tsdb: Isolation for writes Aug 13, 2019
@roidelapluie
Copy link
Member

@beorn7 @brian-brazil this can be closed, right?

@prometheus prometheus locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants