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

Handle conflicts on replication of desynchronized node #8

Open
Trayshar opened this issue Jan 17, 2023 · 0 comments
Open

Handle conflicts on replication of desynchronized node #8

Trayshar opened this issue Jan 17, 2023 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@Trayshar
Copy link
Contributor

Trayshar commented Jan 17, 2023

  1. Node A and Node B are not connected
  2. Change the same data on each Node
  3. Connect Node A and Node B
  4. Replication will commence, but data will not get synchronized. Either the change gets overwritten or a conflict occurs

Possible solution: Prioritize "HAMCLOUD Main Nodes" over all others, use latest data. Possible data loss.

Further work is needed to evaluate which solutions works best for us.

@Trayshar Trayshar added bug Something isn't working help wanted Extra attention is needed labels Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant