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

[Remote Store] Handle transient and permanent un-availability of the remote store #3397

Closed
sachinpkale opened this issue May 19, 2022 · 2 comments
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request

Comments

@sachinpkale
Copy link
Member

Describe the solution you'd like
When remote store is un-available, either we need to stop ingestion in order to keep the durability guarantees or ingestion continues and data is back-filled once remote store is available. There are various scenarios that need to be considered while handling these failures. This task describes all such scenarios and provide implementation.

@sachinpkale sachinpkale added enhancement Enhancement or improvement to existing feature or request untriaged labels May 19, 2022
@ashking94
Copy link
Member

we have implemented refresh retry and remote segments upload backpressure - #7363 and #6851.

@ashking94
Copy link
Member

@sachinpkale closing this issue for now. Lets think if there are more things that we can add and reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request
Projects
None yet
Development

No branches or pull requests

4 participants