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

add pool split-brain protection #409

Open
KaymeKaydex opened this issue Oct 1, 2024 · 3 comments
Open

add pool split-brain protection #409

KaymeKaydex opened this issue Oct 1, 2024 · 3 comments
Labels
needs feedback Something is unclear with the issue

Comments

@KaymeKaydex
Copy link

KaymeKaydex commented Oct 1, 2024

now the pool will not react in any way to the fact that 2 masters have appeared in the single master topology

I propose to introduce a double master type of behavior and return errors by default instead of executing a request to the pool

@KaymeKaydex KaymeKaydex changed the title add split-brain protection add pool split-brain protection Oct 1, 2024
@oleg-jukovec
Copy link
Collaborator

oleg-jukovec commented Oct 1, 2024

How would you propose to implement this?

@oleg-jukovec oleg-jukovec added question Further information is requested needs feedback Something is unclear with the issue and removed question Further information is requested labels Oct 1, 2024
@KaymeKaydex
Copy link
Author

Now I assume that the best solution would be some processing on the pool balancer interface. Get the total number of masters from them and make policies that will decide what to do in this case

however, I assume that this is blocked by the solution with balancers #400 . I tried to correctly prepare this interface in one go, but this clearly requires more effort

@KaymeKaydex
Copy link
Author

I believe this policy will not allow you to completely protect against split brain, but it will allow you to quickly stop it if this was not intended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs feedback Something is unclear with the issue
Projects
None yet
Development

No branches or pull requests

2 participants