Skip to content

Commit 2fbc2d3

Browse files
Merge pull request #212201 from VandhanaMehta/HA+ReadReplicaGA
doc updates for HA with read replica GA
2 parents 5ead9ab + cecb6d3 commit 2fbc2d3

File tree

5 files changed

+16
-7
lines changed

5 files changed

+16
-7
lines changed

articles/mysql/flexible-server/concepts-high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ You can disable HA on a server after you create it. Billing stops immediately.
163163
You need to be able to mitigate downtime for your application even when you're not using HA. Service downtime, like scheduled patches, minor version upgrades, or customer-initiated operations like scaling of compute can be performed during scheduled maintenance windows. To mitigate application impact for Azure-initiated maintenance tasks, you can schedule them on a day of the week and time that minimizes the impact on the application.</br>
164164

165165
- **Can I use a read replica for an HA-enabled server?**</br>
166-
Read replicas aren't supported for HA servers. This feature is on our roadmap, and we're working to make it available soon.</br>
166+
Yes, read replicas are supported for HA servers.</br>
167167

168168
- **Can I use Data-in Replication for HA servers?**</br>
169169
Data-in Replication isn't supported for HA servers. But Data-in Replication for HA servers is on our roadmap and will be available soon. For now, if you want to use Data-in Replication for migration, you can follow these steps:

articles/mysql/flexible-server/concepts-read-replicas.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,9 @@ Azure Database for MySQL Flexible Server provides the **Replication lag in secon
7575

7676
If you see increased replication lag, refer to [troubleshooting replication latency](./../howto-troubleshoot-replication-latency.md) to troubleshoot and understand possible causes.
7777

78+
>[!IMPORTANT]
79+
>Read Replica on HA server uses storage based replication technology, which no longer uses 'SLAVE_IO_RUNNING' metric available in MySQL's 'SHOW SLAVE STATUS' command. The value of it will always be displayed as "No" and is not indicative of replication status.
80+
7881
## Stop replication
7982

8083
You can stop replication between a source and a replica. After replication is stopped between a source server and a read replica, the replica becomes a standalone server. The data in the standalone server is the data that was available on the replica at the time the stop replication command was started. The standalone server doesn't catch up with the source server.
@@ -138,7 +141,6 @@ If GTID is enabled on a source server (`gtid_mode` = ON), newly created replicas
138141

139142
| Scenario | Limitation/Consideration |
140143
|:-|:-|
141-
| Replica on server with HA enabled | Not supported |
142144
| Replica on server in Burstable Pricing Tier| Not supported |
143145
| Cross region read replication | Not supported |
144146
| Pricing | The cost of running the replica server is based on the region where the replica server is running |

articles/mysql/flexible-server/how-to-read-replicas-cli.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ In this article, you will learn how to create and manage read replicas in the Az
1818

1919
[!Note]
2020
>
21-
> * Replica is not supported on high availability enabled server.
22-
>
2321
> * If GTID is enabled on a primary server (`gtid_mode` = ON), newly created replicas will also have GTID enabled and use GTID based replication. To learn more refer to [Global transaction identifier (GTID)](concepts-read-replicas.md#global-transaction-identifier-gtid)
2422
2523
## Azure CLI

articles/mysql/flexible-server/how-to-read-replicas-portal.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,7 @@ ms.date: 06/17/2021
1616
In this article, you will learn how to create and manage read replicas in the Azure Database for MySQL flexible server using the Azure portal.
1717

1818
> [!Note]
19-
>
20-
> * Replica is not supported on high availability enabled server.
21-
>
19+
>
2220
> * If GTID is enabled on a primary server (`gtid_mode` = ON), newly created replicas will also have GTID enabled and use GTID based replication. To learn more refer to [Global transaction identifier (GTID)](concepts-read-replicas.md#global-transaction-identifier-gtid)
2321
2422
## Prerequisites

articles/mysql/flexible-server/whats-new.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,17 @@ This article summarizes new releases and features in Azure Database for MySQL -
2323
> This article contains references to the term slave, a term that Microsoft no longer uses. When the term is removed from the software, we'll remove it from this article.
2424
2525
## September 2022
26+
- **Read replica for HA enabled Azure Database for MySQL - Flexible Server (General Availability)**
27+
28+
The read replica feature allows you to replicate data from an Azure Database for MySQL flexible server to a read-only server. You can replicate the source server to up to 10 replicas. This functionality is now extended to support HA enabled servers within same region.[Learn more](concepts-read-replicas.md)
29+
30+
31+
32+
- **Azure Active Directory authentication for Azure Database for MySQL – Flexible Server (Public Preview)**
33+
34+
You can now authenticate to Azure Database for MySQL - Flexible server using Microsoft Azure Active Directory (Azure AD) using identities. With Azure AD authentication, you can manage database user identities and other Microsoft services in a central location, which simplifies permission management. [Learn More](concepts-azure-ad-authentication.md)
35+
36+
2637

2738
- **Customer managed keys data encryption – Azure Database for MySQL – Flexible Server (Preview)**
2839

0 commit comments

Comments
 (0)