Skip to content

Commit 36d59e4

Browse files
authored
Update advisor-reference-reliability-recommendations.md
Link fixes and inclusive language
1 parent d0977f8 commit 36d59e4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/advisor/advisor-reference-reliability-recommendations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -285,15 +285,15 @@ Learn more about [Kubernetes service - ClustersUsingBSeriesVMs (Clusters having
285285

286286
As previously announced, Azure Data Lake Storage Gen1 will be retired on February 29, 2024. We highly recommend migrating your data lake to Azure Data Lake Storage Gen2, which offers advanced capabilities specifically designed for big data analytics and is built on top of Azure Blob Storage.
287287

288-
Learn more about [Data lake store account - ADLSGen1_Deprecation (You have ADLS Gen1 Accounts Which Needs to be Migrated to ADLS Gen2)](azure/updates/action-required-switch-to-azure-data-lake-storage-gen2-by-29-february-2024/).
288+
Learn more about [Data lake store account - ADLSGen1_Deprecation (You have ADLS Gen1 Accounts Which Needs to be Migrated to ADLS Gen2)](/azure/updates/action-required-switch-to-azure-data-lake-storage-gen2-by-29-february-2024/).
289289

290290
## MySQL
291291

292292
### Replication - Add a primary key to the table that currently does not have one
293293

294-
Based on our internal monitoring, we have observed significant replication lag on your replica server. This lag is occurring because the replica server is replaying relay logs on a table that lacks a primary key. To ensure that the replica server can effectively synchronize with the master and keep up with changes, we highly recommend adding primary keys to the tables in the master server and subsequently recreating the replica server.
294+
Based on our internal monitoring, we have observed significant replication lag on your replica server. This lag is occurring because the replica server is replaying relay logs on a table that lacks a primary key. To ensure that the replica server can effectively synchronize with the primary and keep up with changes, we highly recommend adding primary keys to the tables in the primary server and subsequently recreating the replica server.
295295

296-
Learn more about [Azure Database for MySQL flexible server - MySqlFlexibleServerReplicaMissingPKfb41 (Replication - Add a primary key to the table that currently does not have one)](azure/mysql/how-to-troubleshoot-replication-latency#no-primary-key-or-unique-key-on-a-table).
296+
Learn more about [Azure Database for MySQL flexible server - MySqlFlexibleServerReplicaMissingPKfb41 (Replication - Add a primary key to the table that currently does not have one)](/azure/mysql/how-to-troubleshoot-replication-latency#no-primary-key-or-unique-key-on-a-table).
297297

298298
### High Availability - Add primary key to the table that currently does not have one.
299299

0 commit comments

Comments
 (0)