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.

Sign up for GitHub

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

update(postgresql): primary & replica replacement timeout #589

Merged
merged 1 commit into from
Dec 6, 2024
Merged

update(postgresql): primary & replica replacement timeout #589

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 19 additions & 16 deletions docs/products/postgresql/concepts/upgrade-failover.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,25 +32,25 @@ different procedures in case of primary or replica nodes disconnections.

### Primary server disconnection

If the **primary** server disappears, Aiven's management platform uses
a **60-second timeout** before marking the server as down and promoting
a replica server as new primary. During this 60-second timeout, the
master is unavailable (`servicename-projectname.aivencloud.com` does not
respond), and `replica-servicename-projectname.aivencloud.com` works
fine (in read-only mode).

After the replica promotion, `servicename-projectname.aivencloud.com`
would point to the new primary server, while
`replica-servicename-projectname.aivencloud.com` becomes unreachable.
Finally, a new replica server is created, and after the synchronisation
with the primary, the `replica-servicename-projectname.aivencloud.com`
DNS is switched to point to the new replica server.
If the primary server disappears, Aiven's management platform uses an initial 60-second
timeout before marking the server as down and promoting a replica server as new primary.
During this 60-second timeout, the master is unavailable
(`servicename-projectname.aivencloud.com` does not respond), and
`replica-servicename-projectname.aivencloud.com` works fine (in read-only mode).

After the replica promotion, `servicename-projectname.aivencloud.com` would point to the
new primary server, while `replica-servicename-projectname.aivencloud.com` becomes
unreachable. Finally, a new replica server is created, and after the synchronisation with
the primary, the `replica-servicename-projectname.aivencloud.com` DNS is switched to point
to the new replica server.

Recovery time can take up to 180 seconds depending on client side settings and when in the
DNS TTL cycle the disconnection occurs.

### Replica server disconnection

If the **replica** server disappears, Aiven's management platform uses
a **60-second timeout** before marking the server as down and creating a
new replica server.
If the replica server disappears, Aiven's management platform uses an initial 60-second
timeout before marking the server as down and creating a new replica server.

:::note
Each Aiven for PostgreSQL® Business plan supports one replica server
Expand All @@ -69,6 +69,9 @@ The DNS record pointing to primary server
`SERVICE_NAME-PROJECT_NAME.aivencloud.com` remains unchanged during the
recovery of the replica server.

Recovery time can take up to 180 seconds depending on client side settings and when in the
DNS TTL cycle the disconnection occurs.

## Controlled switchover during upgrades or migrations

:::note
Expand Down
Loading