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

Tree-service sync after splitbrain failover #2127

Closed
anatoly-bogatyrev opened this issue Dec 2, 2022 · 2 comments · Fixed by #2161
Closed

Tree-service sync after splitbrain failover #2127

anatoly-bogatyrev opened this issue Dec 2, 2022 · 2 comments · Fixed by #2161
Assignees
Labels
bug Something isn't working U2 Seriously planned
Milestone

Comments

@anatoly-bogatyrev
Copy link

anatoly-bogatyrev commented Dec 2, 2022

Incorrect tree-service sync after splitbrain failover.

Synchronization occurs only from one node.
In this case, the node could synchronize data with a node from the same part of the cluster.
The order for the container is fixed.

Need to fix this:

  • get not fixed node to sync (can be selected sequentially or in random)
  • sync not only after new epoch event
@alexchetaev alexchetaev added the U3 Regular label Dec 2, 2022
@fyrchik
Copy link
Contributor

fyrchik commented Dec 8, 2022

Let's add randomization for now and discuss other ways to improve the syncronization.

@alexchetaev
Copy link

Need to create issue for discussion

@alexchetaev alexchetaev added U2 Seriously planned and removed U3 Regular labels Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working U2 Seriously planned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants