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

Remove chunks storage support #5

Closed
pracucci opened this issue Jul 16, 2021 · 16 comments · Fixed by #715
Closed

Remove chunks storage support #5

pracucci opened this issue Jul 16, 2021 · 16 comments · Fixed by #715
Assignees

Comments

@pracucci
Copy link
Collaborator

Mimir should remove support for the chunks storage.

@simonswine
Copy link
Contributor

simonswine commented Nov 24, 2021

I have started removing chunks of storage in the ingester code path.

All things that should be addressed as part of this work, but not in a particular PR I have marked with TODO: (remove-chunks)

I think those are the next next tasks I could foresee:

@simonswine simonswine self-assigned this Nov 24, 2021
@09jvilla
Copy link
Contributor

@simonswine should the list above include anything about the purger, which I believe is only relevant for chunks?

@pstibrany
Copy link
Member

Beware that purger exposes API for deleting tenants when using blocks storage.

@09jvilla
Copy link
Contributor

So does that mean the purger can't be removed @pstibrany ?

I was going off of this docs page:
https://cortexmetrics.io/docs/guides/deleting-series/
which says deletion is only supported for chunks and that deletion involves the use of the "purger" service.

@09jvilla
Copy link
Contributor

Ah I just re-read your comment...
so are you saying that the purger can't be used in blocks storage for targeted deletion of time series, but it can be used to delete an entire tenant?
When you say "delete an entire tenant", I assume you mean all blocks that belong to that tenant?

@pracucci
Copy link
Collaborator Author

so are you saying that the purger can't be used in blocks storage for targeted deletion of time series, but it can be used to delete an entire tenant?

Correct.

When you say "delete an entire tenant", I assume you mean all blocks that belong to that tenant?

Correct.

@09jvilla
Copy link
Contributor

@09jvilla
Copy link
Contributor

do you intend to keep these endpoints around now that there is the ability to configure per-tenant retention? I see they are still marked as "experimental"

@pracucci
Copy link
Collaborator Author

everything can be removed except https://cortexmetrics.io/docs/api/#tenant-delete-request and https://cortexmetrics.io/docs/api/#tenant-delete-status?

I think so.

do you intend to keep these endpoints around now that there is the ability to configure per-tenant retention?

Yes, we do.

@09jvilla
Copy link
Contributor

09jvilla commented Dec 1, 2021

Thanks @pracucci . I created #555 and added it to the list.

@09jvilla
Copy link
Contributor

09jvilla commented Dec 2, 2021

@simonswine would any of the existing issues under this epic cover removing limits.max_chunks_per_query ? I see this marked as a flag to remove in our spreadsheet with a pointer to this issue. Just want to make sure it doesn't get lost - I can always make another issue if needed.

It seems like if we did this, we would also want to set querier.max-fetched-chunks-per-query': '1500000, but only for the ruler (not for any other components). Seems like we would leave the default to 0 (i.e. unset), but selectively set this on the ruler. Then again, I'm not even sure how easy that is to do since you'd have to do it with the CLI flag. At minimum, seems like you couldn't do it if you were running as target=all.

@pracucci
Copy link
Collaborator Author

PR to remove chunks purger: #743

@pracucci
Copy link
Collaborator Author

PR to remove table manager logic: #744

@pracucci
Copy link
Collaborator Author

PR to remove tombstones and cache gen support (used by series deletion supported only by chunks storage): #748

@pracucci
Copy link
Collaborator Author

PR to remove chunks storage support from querier: #753

@osg-grafana osg-grafana linked a pull request Jan 14, 2022 that will close this issue
@pracucci
Copy link
Collaborator Author

pracucci commented Jan 14, 2022

From now on I will keep track of remaining work in this comment, that I will edit over time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants