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

Slave promotion #52

Open
frodolooijaard opened this issue Feb 28, 2020 · 0 comments
Open

Slave promotion #52

frodolooijaard opened this issue Feb 28, 2020 · 0 comments

Comments

@frodolooijaard
Copy link

I am currently evaluating pglookout for our needs. One scenario is as follows:
We have three sites, one with the master database (1), two with one slave database each: (2) and (3).
On all three sites pglookout is running. The pglookout on site (3) is also used as observer for sites (1) and (2).

Starting from a stable situation, we make communication between the sites (1) and (2) impossible. Site (3) can still communicate with both site (1) and (2).

Now on site (2) pglookout promotes the slave to master, even though it knows from the observer that it still can see a master on site (1). But it seems it does not take the information from the observer into account at all when making the decision to promote.

Should the promotion decision not be based on observer data too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant