Skip to content

Ingester flushes queued chunks while sending to another ingester #775

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
bboreham opened this issue Mar 27, 2018 · 2 comments
Closed

Ingester flushes queued chunks while sending to another ingester #775

bboreham opened this issue Mar 27, 2018 · 2 comments

Comments

@bboreham
Copy link
Contributor

If the transfer succeeds then the same data is going to be flushed again by the new ingester.

If the transfer fails then the ingester will attempt to flush everything, so maybe it's a benefit that we kept on flushing regardless, but I think it would be better to optimise the happy path.

@gouthamve
Copy link
Contributor

This is much less of an issue when using the WAL (statefulset) because there is no handover.

@bboreham bboreham added the storage/chunks Chunks storage engine label Jun 10, 2021
@alanprot
Copy link
Member

Chunks storage was removed.

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

No branches or pull requests

4 participants