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] Integrate translog download in failover (replica-primary promotion) #5637

Closed
Tracked by #5671
ashking94 opened this issue Dec 26, 2022 · 2 comments
Closed
Tracked by #5671
Labels
distributed framework enhancement Enhancement or improvement to existing feature or request Storage:Durability Issues and PRs related to the durability framework v2.5.0 'Issues and PRs related to version v2.5.0'

Comments

@ashking94
Copy link
Member

ashking94 commented Dec 26, 2022

Is your feature request related to a problem? Please describe.
For remote backed indices with remote translog enabled, the incoming write request by the client gets served by the primary shard. In a pure local storage backed index, when a write request lands on the primary, the same is stored as a translog and then request fans out to all eligible replicas where the request is replayed similarly as the primary. With remote store backed translog, the translog is stored only on the primary along with remote store for durability and replicas are not subjected to translog. With this, now whenever a replica to primary promotion happens, there is a need for the translog to be downloaded from remote store and be played against the engine.

Describe the solution you'd like
Integrate remote translog download with failover.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@ashking94 ashking94 added enhancement Enhancement or improvement to existing feature or request untriaged Storage:Durability Issues and PRs related to the durability framework v2.5.0 'Issues and PRs related to version v2.5.0' distributed framework and removed untriaged labels Dec 26, 2022
@saratvemulapalli
Copy link
Member

@ashking94 this is labelled 2.5, code freeze is 1/10 do you think you can make it?

@ashking94
Copy link
Member Author

@saratvemulapalli this will be closed before the code freeze.

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 Storage:Durability Issues and PRs related to the durability framework v2.5.0 'Issues and PRs related to version v2.5.0'
Projects
None yet
Development

No branches or pull requests

2 participants