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] Integration of remote translog and remote segment store #3754

Closed
Tracked by #5671
sachinpkale opened this issue Jul 1, 2022 · 0 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

Comments

@sachinpkale
Copy link
Member

Describe the solution you'd like

  • Once remote segment store and remote translog are implemented, the next step is to make sure that both of these stores are in sync.
  • Today, translog and segment store on local work together in order to provide consistent experience of the indexed data. This involves purging the translog only after commit is successful and all the segment files are fsynced to the disk
  • For an OpenSearch cluster with remote store enabled, we have:
    • Remote Translog
    • Local Segment Store
    • Remote Segment Store
  • In this issue, we will discuss different approaches to keep all the three stores mentioned above in sync.
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
Projects
None yet
Development

No branches or pull requests

3 participants