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

failover: select the furthest replicated node with the highest identifier #21

Merged
merged 2 commits into from
Nov 26, 2015

Conversation

saaros
Copy link
Contributor

@saaros saaros commented Nov 26, 2015

If there are multiple nodes with the same replication positions pick the one
with the "highest" name to make sure pglookouts running on all standbys make
the same decision.  The rationale for picking the "highest" node is that
there's no obvious way for pglookout to decide which of the nodes is "best"
beyond looking at replication positions, but picking the highest id supports
environments where nodes are assigned identifiers from an incrementing
sequence identifiers and where we want to promote the latest and greatest
node.  In static environments node identifiers can be priority numbers, with
the highest number being the one that should be preferred.

…fier

If there are multiple nodes with the same replication positions pick the one
with the "highest" name to make sure pglookouts running on all standbys make
the same decision.  The rationale for picking the "highest" node is that
there's no obvious way for pglookout to decide which of the nodes is "best"
beyond looking at replication positions, but picking the highest id supports
environments where nodes are assigned identifiers from an incrementing
sequence identifiers and where we want to promote the latest and greatest
node.  In static environments node identifiers can be priority numbers, with
the highest number being the one that should be preferred.
Ormod added a commit that referenced this pull request Nov 26, 2015
failover: select the furthest replicated node with the highest identifier
@Ormod Ormod merged commit cfe8473 into Aiven-Open:master Nov 26, 2015
@saaros saaros deleted the select_highest_node branch May 12, 2016 07:32
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

Successfully merging this pull request may close these issues.

2 participants