Skip to content

Commit 427f59e

Browse files
authored
Merge pull request #96242 from rachel-msft/edits1117
Update rule inheritance
2 parents 12fc63a + 880d7d7 commit 427f59e

File tree

3 files changed

+12
-6
lines changed

3 files changed

+12
-6
lines changed

articles/mariadb/concepts-read-replicas.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mariadb
77
ms.topic: conceptual
8-
ms.date: 09/06/2019
8+
ms.date: 11/17/2019
99
---
1010

1111
# Read replicas in Azure Database for MariaDB
@@ -69,7 +69,7 @@ Learn how to [create a read replica in the Azure portal](howto-read-replicas-por
6969

7070
## Connect to a replica
7171

72-
When you create a replica, it doesn't inherit the firewall rules or VNet service endpoint of the master server. These rules must be set up independently for the replica.
72+
At creation, a replica inherits the firewall rules or VNet service endpoint of the master server. Afterwards, these rules are independent from the the master server.
7373

7474
The replica inherits the admin account from the master server. All user accounts on the master server are replicated to the read replicas. You can only connect to a read replica by using the user accounts that are available on the master server.
7575

@@ -122,6 +122,8 @@ A replica is created by using the same server configuration as the master. After
122122
> [!IMPORTANT]
123123
> Before a master server configuration is updated to new values, update the replica configuration to equal or greater values. This action ensures the replica can keep up with any changes made to the master.
124124
125+
Firewall rules, virtual network rules, and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
126+
125127
### Stopped replicas
126128

127129
If you stop replication between a master server and a read replica, the stopped replica becomes a standalone server that accepts both reads and writes. The standalone server can't be made into a replica again.

articles/mysql/concepts-read-replicas.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 09/06/2019
8+
ms.date: 11/17/2019
99
---
1010

1111
# Read replicas in Azure Database for MySQL
@@ -64,7 +64,7 @@ Learn how to [create a read replica in the Azure portal](howto-read-replicas-por
6464

6565
## Connect to a replica
6666

67-
When you create a replica, it doesn't inherit the firewall rules or VNet service endpoint of the master server. These rules must be set up independently for the replica.
67+
At creation, a replica inherits the firewall rules or VNet service endpoint of the master server. Afterwards, these rules are independent from the the master server.
6868

6969
The replica inherits the admin account from the master server. All user accounts on the master server are replicated to the read replicas. You can only connect to a read replica by using the user accounts that are available on the master server.
7070

@@ -117,6 +117,8 @@ A replica is created by using the same server configuration as the master. After
117117
> [!IMPORTANT]
118118
> Before a master server configuration is updated to new values, update the replica configuration to equal or greater values. This action ensures the replica can keep up with any changes made to the master.
119119
120+
Firewall rules, virtual network rules, and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
121+
120122
### Stopped replicas
121123

122124
If you stop replication between a master server and a read replica, the stopped replica becomes a standalone server that accepts both reads and writes. The standalone server can't be made into a replica again.

articles/postgresql/concepts-read-replicas.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: rachel-msft
55
ms.author: raagyema
66
ms.service: postgresql
77
ms.topic: conceptual
8-
ms.date: 09/06/2019
8+
ms.date: 11/17/2019
99
---
1010

1111
# Read replicas in Azure Database for PostgreSQL - Single Server
@@ -155,7 +155,9 @@ A replica is created by using the same compute and storage settings as the maste
155155
156156
PostgreSQL requires the value of the `max_connections` parameter on the read replica to be greater than or equal to the master value; otherwise, the replica won't start. In Azure Database for PostgreSQL, the `max_connections` parameter value is based on the SKU. For more information, see [Limits in Azure Database for PostgreSQL](concepts-limits.md).
157157

158-
If you try to update the server values, but don't adhere to the limits, you receive an error.
158+
If you try to update the server values described above, but don't adhere to the limits, you receive an error.
159+
160+
Firewall rules, virtual network rules, and parameter settings are not inherited from the master server to the replica when the replica is created or afterwards.
159161

160162
### max_prepared_transactions
161163
[PostgreSQL requires](https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS) the value of the `max_prepared_transactions` parameter on the read replica to be greater than or equal to the master value; otherwise, the replica won't start. If you want to change `max_prepared_transactions` on the master, first change it on the replicas.

0 commit comments

Comments
 (0)