From a2b1ed771a70604f4b01429c427f7480c4ae8b6f Mon Sep 17 00:00:00 2001 From: Dorota Wojcik Date: Wed, 7 Aug 2024 11:58:28 +0200 Subject: [PATCH] feedback --- ...ilability-mysql.md => high-availability.md} | 18 +++++++++--------- .../postgresql/concepts/high-availability.md | 18 +++++++++--------- sidebars.ts | 2 +- 3 files changed, 19 insertions(+), 19 deletions(-) rename docs/products/mysql/concepts/{high-availability-mysql.md => high-availability.md} (84%) diff --git a/docs/products/mysql/concepts/high-availability-mysql.md b/docs/products/mysql/concepts/high-availability.md similarity index 84% rename from docs/products/mysql/concepts/high-availability-mysql.md rename to docs/products/mysql/concepts/high-availability.md index f0c50376..381d51e4 100644 --- a/docs/products/mysql/concepts/high-availability-mysql.md +++ b/docs/products/mysql/concepts/high-availability.md @@ -3,19 +3,19 @@ title: High availability of Aiven for MySQL® sidebar_label: High availability --- -Aiven for MySQL® is available on a variety of plans, offering different levels of high availability. The selected plan defines the features available. +Aiven for MySQL® is available on a variety of plans, offering different levels of service availability. The selected plan defines the features available. -| Plan | High availability features | Backup history | -| ------------ | ------------------------------------------------------------------------------- | -------------- | -| **Hobbyist** | Single node with limited availability | 2 days | -| **Startup** | Single node with limited availability | 2 days | -| **Business** | Two nodes (primary + standby: with higher availability) | 14 days | -| **Premium** | Three nodes (primary + 2 x standby: with top high availability characteristics) | 30 days | +| Plan | Service availability features | Backup history | +| ------------ | -------------------------------------------------------------------------- | -------------- | +| **Hobbyist** | Single node (limited availability) | 2 days | +| **Startup** | Single node (limited availability) | 2 days | +| **Business** | 1 primary node and 1 standby node (higher availability) | 14 days | +| **Premium** | 1 primary node and 2 standby nodes (top high availability characteristics) | 30 days | ## Primary and standby nodes Aiven's Business and Premium plans offer a primary node and standby nodes. -A standby service is useful for multiple reasons: +A standby node is useful for multiple reasons: - Provides another physical copy of the data in case of hardware, software, or network failures @@ -41,7 +41,7 @@ network access is restored. Severe failures, such as losing a node entirely in case of hardware or severe software problems, require radical recovery measures. The Aiven monitoring infrastructure automatically detects a failing node -both when the node starts reporting issues in the self-diagnostics or +when the node starts reporting issues in the self-diagnostics or when it stops communicating. In such cases, the monitoring infrastructure automatically schedules a new replacement node to be created. diff --git a/docs/products/postgresql/concepts/high-availability.md b/docs/products/postgresql/concepts/high-availability.md index 5067bd3c..bea3c1a4 100644 --- a/docs/products/postgresql/concepts/high-availability.md +++ b/docs/products/postgresql/concepts/high-availability.md @@ -3,21 +3,21 @@ title: High availability of Aiven for PostgreSQL® sidebar_label: High availability --- -Aiven for PostgreSQL® is available on a variety of plans, offering different levels of high availability. The selected plan defines the features available. +Aiven for PostgreSQL® is available on a variety of plans, offering different levels of service availability. The selected plan defines the features available. -| Plan | High availability features | Backup history | -| ------------ | ------------------------------------------------------------------------------- | -------------- | -| **Hobbyist** | Single node with limited availability | 2 days | -| **Startup** | Single node with limited availability | 2 days | -| **Business** | Two nodes (primary + standby: with higher availability) | 14 days | -| **Premium** | Three nodes (primary + 2 x standby: with top high availability characteristics) | 30 days | +| Plan | Service availability features | Backup history | +| ------------ | -------------------------------------------------------------------------- | -------------- | +| **Hobbyist** | Single node (limited availability) | 2 days | +| **Startup** | Single node (limited availability) | 2 days | +| **Business** | 1 primary node and 1 standby node (higher availability) | 14 days | +| **Premium** | 1 primary node and 2 standby nodes (top high availability characteristics) | 30 days | ## Primary and standby nodes Aiven's Business and Premium plans offer a [primary node](/docs/products/postgresql/reference/terminology) and [standby nodes](/docs/products/postgresql/reference/terminology). -A standby service is useful for multiple reasons: +A standby node is useful for multiple reasons: - Provides another physical copy of the data in case of hardware, software, or network failures @@ -43,7 +43,7 @@ network access is restored. Severe failures, such as losing a node entirely in case of hardware or severe software problems, require radical recovery measures. The Aiven monitoring infrastructure automatically detects a failing node -both when the node starts reporting issues in the self-diagnostics or +when the node starts reporting issues in the self-diagnostics or when it stops communicating. In such cases, the monitoring infrastructure automatically schedules a new replacement node to be created. diff --git a/sidebars.ts b/sidebars.ts index b225016b..75cfe412 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -1666,7 +1666,7 @@ const sidebars: SidebarsConfig = { 'products/mysql/concepts/mysql-memory-usage', 'products/mysql/concepts/mysql-replication', 'products/mysql/concepts/mysql-tuning-and-concurrency', - 'products/mysql/concepts/high-availability-mysql', + 'products/mysql/concepts/high-availability', ], },