You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: