-
Notifications
You must be signed in to change notification settings - Fork 8
Export merge tree partition on replicated engine #1072
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
base: antalya-25.6.5
Are you sure you want to change the base?
Conversation
Very drafty for now. Created the PR so I can take notes of things I still need to implement / ideas. Also to get cicd report |
TODO list from the top of my head:
|
The first thing that comes to mind is to create an in-memory list of references to those parts as soon as the replicas get notified about a partition export. All replicas will references to all parts, even if they are not responsible for exporting a given part. This should be restored upon bootup. There is one small time window in which this could fail: if between the time the export was published in zookeeper and the replicas are notified the part is completely deleted from all replicas. It seems rare enough and we can probably live with it. |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: