Skip to content

Write ahead log ingester #12

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

Closed
jml opened this issue Sep 9, 2016 · 0 comments · Fixed by #1103
Closed

Write ahead log ingester #12

jml opened this issue Sep 9, 2016 · 0 comments · Fixed by #1103
Labels
component/ingester postmortem An issue arising out of a serious production issue type/feature

Comments

@jml
Copy link
Contributor

jml commented Sep 9, 2016

From @tomwilkie

We need this so that when ingesters go away, we don't lose their data.

Copied from original issue: tomwilkie/frankenstein#11

@jml jml modified the milestone: Dogfooding Sep 9, 2016
@jml jml added the postmortem An issue arising out of a serious production issue label Dec 12, 2016
@tomwilkie tomwilkie removed this from the Dogfooding milestone Jan 6, 2017
roystchiang pushed a commit to roystchiang/cortex that referenced this issue Apr 6, 2022
…/422-on-chunk-limits

Returning 422 (instead 500) when query hit max_chunks_per_query limit…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ingester postmortem An issue arising out of a serious production issue type/feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants