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

Make rule evaluation and federation consistent in time #1893

Open
beorn7 opened this Issue Aug 15, 2016 · 8 comments

Comments

Projects
None yet
5 participants
@beorn7
Copy link
Member

beorn7 commented Aug 15, 2016

Currently, if samples get ingested during a rule is evaluated or a federation request is processed, only a subset of samples with the same timestamp may be taken into account during the evaluation.

Making ingestion of all the samples from a single scrape atomic would solve the problem, but the problem might be solved in an easier way by "simply" ignoring samples that came in after a certain watermark.

For reference: discussion started in prometheus/docs#514 and already referenced #398 as a possible part of the solution.

@beorn7

This comment has been minimized.

Copy link
Member Author

beorn7 commented Aug 15, 2016

Also #1887 for the reported incident that caused the discussion in the first place.

@lmb

This comment has been minimized.

Copy link

lmb commented Apr 11, 2017

I reported #2598, which was closed as a duplicate of this issue. I think this issue should mention that this behaviour breaks aggregating histograms using histogram_quantile in the currently released version. That should prevent more dupes.

@gouthamve

This comment has been minimized.

Copy link
Member

gouthamve commented Jun 14, 2017

AFAICS, this is fixed 2.0. Can this be closed @fabxc @brian-brazil

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 14, 2017

This is not fixed in 2.0 (yet).

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 22, 2017

I've got a basic version of this working over in the tsdb repo, it needs cleanup and performance work.

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Dec 12, 2018

@beorn7 , @brian-brazil , @gouthamve is this issue still unsolved?

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 12, 2018

Yes, there's an old PR over in TSDB for this. I believe @gouthamve was planning on working on it soon.

@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented Dec 12, 2018

aah that must be the isolation PR prometheus/tsdb#306

@gouthamve gouthamve referenced this issue Dec 12, 2018

Open

Isolation #306

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.