mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-01 17:08:30 +02:00
Add documentation for Multi AZ clusters
This commit is contained in:
@@ -16,6 +16,7 @@ Qdrant Cloud offers an optional premium tier for customers who require additiona
|
|||||||
* **Single Sign-On (SSO)**: Premium customers can use their existing SSO provider to manage access to Qdrant Cloud.
|
* **Single Sign-On (SSO)**: Premium customers can use their existing SSO provider to manage access to Qdrant Cloud.
|
||||||
* **VPC Private Links**: Premium customers can connect their Qdrant Cloud clusters to their VPCs using private links.
|
* **VPC Private Links**: Premium customers can connect their Qdrant Cloud clusters to their VPCs using private links.
|
||||||
* **Storage encryption with shared keys**: Premium customers can encrypt their data at rest using their own keys.
|
* **Storage encryption with shared keys**: Premium customers can encrypt their data at rest using their own keys.
|
||||||
|
* **Topology Aware Multi-AZ Setup**: Premium customers can deploy their clusters across multiple availability zones for higher availability and resilience. This guarantees a **99.95% uptime SLA** for Multi-AZ clusters.
|
||||||
|
|
||||||
Please refer to the [Qdrant Cloud SLA](https://qdrant.to/sla/) for a detailed definition on uptime and support SLAs.
|
Please refer to the [Qdrant Cloud SLA](https://qdrant.to/sla/) for a detailed definition on uptime and support SLAs.
|
||||||
|
|
||||||
|
|||||||
@@ -80,6 +80,7 @@ This page shows you how to use the Qdrant Cloud Console to create a custom Qdran
|
|||||||
RAM, the menu provides different options for vCPUs.
|
RAM, the menu provides different options for vCPUs.
|
||||||
1. Select the number of nodes you want the cluster to be deployed on.
|
1. Select the number of nodes you want the cluster to be deployed on.
|
||||||
> Each node is automatically attached with a disk, that has enough space to store data with Qdrant's default collection configuration.
|
> Each node is automatically attached with a disk, that has enough space to store data with Qdrant's default collection configuration.
|
||||||
|
1. Premium tier customers can choose if the cluster should be deployed within a single availability zone, or across multiple availability zones for higher availability and resilience. This can only be chosen during cluster creation and not changed later.
|
||||||
1. Select additional disk space for your deployment.
|
1. Select additional disk space for your deployment.
|
||||||
> Depending on your collection configuration, you may need more disk space per RAM. For example, if you configure `on_disk: true` and only use RAM for caching.
|
> Depending on your collection configuration, you may need more disk space per RAM. For example, if you configure `on_disk: true` and only use RAM for caching.
|
||||||
1. Choose the speed tier for your disk. (AWS only)
|
1. Choose the speed tier for your disk. (AWS only)
|
||||||
@@ -101,6 +102,12 @@ To create a production-ready cluster, you need to ensure the following:
|
|||||||
|
|
||||||
Your cluster should have at least 3 nodes, and each collection should have a replication factor of at least 2. This ensures that is one node fails, or is restarted due to maintenance, a version upgrade, or a scaling operation, that the cluster remains fully operational. You can ensure this by checking the **High Availability** checkbox when creating a cluster.
|
Your cluster should have at least 3 nodes, and each collection should have a replication factor of at least 2. This ensures that is one node fails, or is restarted due to maintenance, a version upgrade, or a scaling operation, that the cluster remains fully operational. You can ensure this by checking the **High Availability** checkbox when creating a cluster.
|
||||||
|
|
||||||
|
**Multi AZ Deployment (Premium only)**
|
||||||
|
|
||||||
|
Premium tier customers can choose to deploy their cluster across multiple availability zones. This ensures that if one availability zone goes down, the cluster remains operational. You can ensure this by checking the **Multi AZ Deployment** checkbox when creating a cluster. This can not be changed later.
|
||||||
|
Multi AZ clusters need a minimum of 3 nodes, and can only scale to a multiple of 3 (e.g. 3, 6, 9, etc.) to ensure that nodes are evenly distributed across availability zones.
|
||||||
|
Your collections should have a replication factor of at least 2 (better 3) to ensure that all data is available in another availability zone, and the outage of one zone is not compromising the availability of the cluster. Shards will be automatically distributed across availability zones, so that each shard has a replica in another availability zone. Traffic is routed between zones automatically, so that the cluster remains available even if one zone goes down.
|
||||||
|
|
||||||
**Disk Speed (AWS only)**
|
**Disk Speed (AWS only)**
|
||||||
|
|
||||||
We recommend the **Balanced** tier for disks >= 32 GiB, and the **Performance** tier for disks >= 256 GiB.
|
We recommend the **Balanced** tier for disks >= 32 GiB, and the **Performance** tier for disks >= 256 GiB.
|
||||||
|
|||||||
@@ -91,7 +91,7 @@ sections:
|
|||||||
oss: false
|
oss: false
|
||||||
free: false
|
free: false
|
||||||
standard: "99.5"
|
standard: "99.5"
|
||||||
premium: "99.9"
|
premium: "Single AZ: 99.9, Multi AZ: 99.95"
|
||||||
- name: Developer Experience
|
- name: Developer Experience
|
||||||
features:
|
features:
|
||||||
- name: Database Web UI
|
- name: Database Web UI
|
||||||
@@ -148,6 +148,11 @@ sections:
|
|||||||
free: false
|
free: false
|
||||||
standard: true
|
standard: true
|
||||||
premium: true
|
premium: true
|
||||||
|
- name: Topology Aware Multi AZ Setup
|
||||||
|
oss: false
|
||||||
|
free: false
|
||||||
|
standard: false
|
||||||
|
premium: true
|
||||||
- name: Disk Performance Tiers
|
- name: Disk Performance Tiers
|
||||||
oss: Depends on chosen infrastructure
|
oss: Depends on chosen infrastructure
|
||||||
free: false
|
free: false
|
||||||
|
|||||||
@@ -37,7 +37,7 @@ tables:
|
|||||||
oss: false
|
oss: false
|
||||||
free: false
|
free: false
|
||||||
standard: "99.5"
|
standard: "99.5"
|
||||||
premium: "99.9"
|
premium: "Single AZ: 99.9, Multi AZ: 99.95"
|
||||||
- name: Automation
|
- name: Automation
|
||||||
oss: false
|
oss: false
|
||||||
free: API, Terraform, Pulumi
|
free: API, Terraform, Pulumi
|
||||||
@@ -53,6 +53,11 @@ tables:
|
|||||||
free: false
|
free: false
|
||||||
standard: true
|
standard: true
|
||||||
premium: true
|
premium: true
|
||||||
|
- name: Topology Aware Multi AZ Setup
|
||||||
|
oss: false
|
||||||
|
free: false
|
||||||
|
standard: false
|
||||||
|
premium: true
|
||||||
- name: Backup & Disaster Recovery
|
- name: Backup & Disaster Recovery
|
||||||
oss: Custom automation
|
oss: Custom automation
|
||||||
free: false
|
free: false
|
||||||
|
|||||||
Reference in New Issue
Block a user