Skip to content

Commit 0594860

Browse files
Merge pull request #203526 from jonels-msft/hsc-replica-promote
Promote replica to R/W
2 parents 8c70b9e + 471cd04 commit 0594860

File tree

4 files changed

+37
-9
lines changed

4 files changed

+37
-9
lines changed

articles/postgresql/hyperscale/concepts-monitoring.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jonels-msft
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: conceptual
9-
ms.date: 06/22/2022
9+
ms.date: 09/27/2022
1010
---
1111

1212
# Monitor and tune Azure Database for PostgreSQL - Hyperscale (Citus)
@@ -60,6 +60,7 @@ These metrics are available for Hyperscale (Citus) nodes:
6060
|memory_percent|Memory percent|Percent|The percentage of memory in use.|
6161
|network_bytes_ingress|Network In|Bytes|Network In across active connections.|
6262
|network_bytes_egress|Network Out|Bytes|Network Out across active connections.|
63+
|replication_lag|Replication Lag|Seconds|How far read replica nodes are behind their counterparts in the primary cluster.|
6364
|storage_percent|Storage percentage|Percent|The percentage of storage used out of the server's maximum.|
6465
|storage_used|Storage used|Bytes|The amount of storage in use. The storage used by the service may include the database files, transaction logs, and the server logs.|
6566

articles/postgresql/hyperscale/concepts-read-replicas.md

Lines changed: 21 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jonels-msft
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: conceptual
9-
ms.date: 06/17/2022
9+
ms.date: 09/27/2022
1010
---
1111

1212
# Read replicas in Azure Database for PostgreSQL - Hyperscale (Citus)
@@ -85,6 +85,25 @@ psql -h c.myreplica.postgres.database.azure.com -U citus@myreplica -d postgres
8585

8686
At the prompt, enter the password for the user account.
8787

88+
## Replica promotion to independent server group
89+
90+
You can promote a replica to an independent server group that is readable and
91+
writable. A promoted replica no longer receives updates from its original, and
92+
promotion can't be undone. Promoted replicas can have replicas of their own.
93+
94+
There are two common scenarios for promoting a replica:
95+
96+
1. **Disaster recovery.** If something goes wrong with the primary, or with an
97+
entire region, you can open another server group for writes as an emergency
98+
procedure.
99+
2. **Migrating to another region.** If you want to move to another region,
100+
create a replica in the new region, wait for data to catch up, then promote
101+
the replica. To avoid potentially losing data during promotion, you may want
102+
to disable writes to the original server group after the replica catches up.
103+
104+
You can see how far a replica has caught up using the `replication_lag`
105+
metric. See [metrics](concepts-monitoring.md#metrics) for more information.
106+
88107
## Considerations
89108

90109
This section summarizes considerations about the read replica feature.
@@ -110,7 +129,7 @@ upscale it on the primary.
110129
Firewall rules and parameter settings aren't inherited from the primary server
111130
to the replica when the replica is created or afterwards.
112131

113-
### Cross-region replication (preview)
132+
### Cross-region replication
114133

115134
Read replicas can be created in the region of the primary server group, or in
116135
any other [region supported by Hyperscale (Citus)](resources-regions.md). The

articles/postgresql/hyperscale/howto-read-replicas-portal.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jonels-msft
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: how-to
9-
ms.date: 06/17/2022
9+
ms.date: 09/27/2022
1010
---
1111

1212
# Create and manage read replicas in Azure Database for PostgreSQL - Hyperscale (Citus) from the Azure portal
@@ -37,7 +37,7 @@ To create a read replica, follow these steps:
3737

3838
4. Enter a name for the read replica.
3939

40-
5. Select a value from the **Location (preview)** drop-down.
40+
5. Select a value from the **Location** drop-down.
4141

4242
6. Select **OK** to confirm the creation of the replica.
4343

@@ -66,6 +66,17 @@ steps:
6666
3. Enter the name of the primary server group to delete. Select **Delete** to
6767
confirm deletion of the primary server group.
6868

69+
## Promote a replica to an independent server group
70+
71+
To promote a server group replica, follow these steps:
72+
73+
1. In the Azure portal, open the **Replication** page for your server group.
74+
75+
2. Select the **Promote** icon for the desired replica.
76+
77+
3. Select the checkbox indicating you understand the action is irreversible.
78+
79+
4. Select **Promote** to confirm.
6980

7081
## Delete a replica
7182

articles/postgresql/hyperscale/product-updates.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.custom: mvc
77
ms.service: postgresql
88
ms.subservice: hyperscale-citus
99
ms.topic: conceptual
10-
ms.date: 07/11/2022
10+
ms.date: 09/27/2022
1111
---
1212

1313
# Product updates for PostgreSQL - Hyperscale (Citus)
@@ -37,9 +37,6 @@ Here are the features currently available for preview:
3737
session and object audit logging via the standard PostgreSQL
3838
logging facility. It produces audit logs required to pass
3939
certain government, financial, or ISO certification audits.
40-
* **[Cross-region
41-
replication](concepts-read-replicas.md#cross-region-replication-preview)**.
42-
Create asynchronous read replicas for a server group in different regions.
4340

4441
## Contact us
4542

0 commit comments

Comments
 (0)