mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-06 19:38:30 +02:00
First round of fixes from review
This commit is contained in:
Bastian Hofmann
@@ -9,13 +9,13 @@ weight: 55
|
||||
|
||||
|
||||
|
||||
Qdrant Cloud provides you with a set of metrics to monitor the health of your database cluster. You can access these metrics in the Qdrant Cloud Console in the **Metrics** and **Request** sections of the cluster details page.
|
||||
Qdrant Cloud provides you with a set of metrics to monitor the health of your database cluster. You can access these metrics in the Qdrant Cloud Console in the **Metrics** and **Request** sections of the Cluster Details page.
|
||||
|
||||
## Logs
|
||||
|
||||
|
||||
|
||||
Logs of the database cluster are available in the Qdrant Cloud Console in the **Logs** section of the cluster details page.
|
||||
Logs of the database cluster are available in the Qdrant Cloud Console in the **Logs** section of the Cluster Details page.
|
||||
|
||||
## Alerts
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ The amount of data is always growing and at some point you might need to change
|
||||
|
||||
Vertical scaling is the process of increasing the capacity of a cluster by adding or removing CPU, storage and memory resources on each database node.
|
||||
|
||||
You can start with a minimal cluster configuration and scale it up over the time to accomodate the growing amount of data in your application. If your cluster consists of several nodes each node will need to be scaled to the same size.
|
||||
You can start with a minimal cluster configuration and scale it up over time to accomodate the growing amount of data in your application. If your cluster consists of several nodes each node will need to be scaled to the same size.
|
||||
|
||||
Note that vertical cluster scaling will require a short downtime, if the collections in your cluster are not replicated. This is because each node of the cluster needs to be restarted to apply the CPU, memory and disk size.
|
||||
|
||||
@@ -27,9 +27,9 @@ Vertical scaling can be an effective way to improve the performance of a cluster
|
||||
|
||||
In such cases, horizontal scaling may be a more effective solution.
|
||||
|
||||
Horizontal scaling, is the process of increasing the capacity of a cluster by adding more nodes and distributing the load and data among them. The horizontal scaling at Qdrant starts on the collection level. You have to choose the number of shards you want to distribute your collection around while creating the collection. Please refer to the [sharding documentation](/documentation/guides/distributed_deployment/#sharding) section for details.
|
||||
Horizontal scaling is the process of increasing the capacity of a cluster by adding more nodes and distributing the load and data among them. The horizontal scaling at Qdrant starts on the collection level. You have to choose the number of shards you want to distribute your collection around while creating the collection. Please refer to the [sharding documentation](/documentation/guides/distributed_deployment/#sharding) section for details.
|
||||
|
||||
When scaling up horizontally, the cloud paltform will automatically rebalance all available shards across nodes to ensure that the data is evenly distributed. See [Configuring Clusters](/documentation/cloud/configure-cluster/#shard-rebalancing) for more details.
|
||||
When scaling up horizontally, the cloud platform will automatically rebalance all available shards across nodes to ensure that the data is evenly distributed. See [Configuring Clusters](/documentation/cloud/configure-cluster/#shard-rebalancing) for more details.
|
||||
|
||||
When scaling down horizontally, the cloud platform will automatically ensure that any shards that are present on the nodes to be deleted, are moved to the remaining nodes.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ weight: 55
|
||||
|
||||
As soon as a new Qdrant version is available. Qdrant Cloud will show you an update notification in the Cluster list and on the Cluster details page.
|
||||
|
||||
To update to a new version, go to the Cluster details page, choose the new version from the version dropdown and click **Update**.
|
||||
To update to a new version, go to the Cluster Details page, choose the new version from the version dropdown and click **Update**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -5,13 +5,13 @@ weight: 55
|
||||
|
||||
# Configure Qdrant Cloud Clusters
|
||||
|
||||
Qdrant Cloud offers several advanced configuration options to optimizer your clusters to your specific needs. You can access these options from the Cluster details page in the Qdrant Cloud console.
|
||||
Qdrant Cloud offers several advanced configuration options to optimize clusters for your specific needs. You can access these options from the Cluster Details page in the Qdrant Cloud console.
|
||||
|
||||
## Collection Defaults
|
||||
|
||||
You can set default values for the configuration of new collections in your cluster. These defaults will be used when creating a new collection, unless you override them in the collection creation request.
|
||||
|
||||
You can configure the default *Replication Factor*, the default *Write Consistency Factor* and if vectors should be stored on disk only, instead of being cached in RAM.
|
||||
You can configure the default *Replication Factor*, the default *Write Consistency Factor*, and if vectors should be stored on disk only, instead of being cached in RAM.
|
||||
|
||||
Refer to [Qdrant Configuration](/documentation/guides/configuration/#configuration-options) for more details.
|
||||
|
||||
@@ -23,7 +23,7 @@ See [Qdrant under the hood: io_uring](/articles/io_uring/#and-what-about-qdrant)
|
||||
|
||||
## Client IP Restrictions
|
||||
|
||||
If configured, only the chosen IP ranges will be allowed to access the cluster. This is useful for securing your cluster and ensuring that only trusted clients can connect to it.
|
||||
If configured, only the chosen IP ranges will be allowed to access the cluster. This is useful for securing your cluster and ensuring that only clients coming from trusted networks can connect to it.
|
||||
|
||||
## Restart Mode
|
||||
|
||||
|
||||
@@ -97,7 +97,7 @@ To create a production-ready cluster, you need to ensure the following:
|
||||
|
||||
**High Availability**
|
||||
|
||||
Your cluster should have at least 3 nodes, and each collection should have a replication factor of at least 2. This ensures that if one node fails, or is being restarted due to maintenance, version upgrades or scaling operations, 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.
|
||||
|
||||
**Backup and Disaster Recovery**
|
||||
|
||||
@@ -105,7 +105,7 @@ You should create a backup schedule for your cluster. This ensures that you can
|
||||
|
||||
**Collection Sharding**
|
||||
|
||||
To allow your cluster to scale horizontally easily, you should configure at least 2 times the shards per collection than the number of nodes in your cluster. You can configure the number of shards when creating a collection. See [**Sharding**](/documentation/guides/distributed_deployment/#sharding) for more information.
|
||||
To allow your cluster to easily scale horizontally, you should configure at least twice as many shards per collection than the number of nodes in your cluster. You can configure the number of shards when creating a collection. See [**Sharding**](/documentation/guides/distributed_deployment/#sharding) for more information.
|
||||
|
||||
If you did not configure enough shards in a collection, you can use the [**Resharding**](/documentation/cloud/cluster-scaling/#resharding) feature to change the number of shards in an existing collection.
|
||||
|
||||
|
||||
@@ -320,7 +320,7 @@ Please refer to the [Resharding](/documentation/cloud/cluster-scaling/#reshardin
|
||||
|
||||
Qdrant allows moving shards between nodes in the cluster and removing nodes from the cluster. This functionality unlocks the ability to dynamically scale the cluster size without downtime. It also allows you to upgrade or migrate nodes without downtime.
|
||||
|
||||
If your cluster is running in Qdrant Cloud, the shards are balanced across the cluster nodes automatically. For more information see the [Configuring Cloud Clusters](/documentation/cloud/configure-cluster/#shard-rebalancing) and [Cloud Cluster Scaling](/documentation/cloud/cluster-scaling/) documentation.
|
||||
If your cluster is running in Qdrant Cloud, shards are balanced across the cluster nodes automatically. For more information see the [Configuring Cloud Clusters](/documentation/cloud/configure-cluster/#shard-rebalancing) and [Cloud Cluster Scaling](/documentation/cloud/cluster-scaling/) documentation.
|
||||
|
||||
Qdrant provides the information regarding the current shard distribution in the cluster with the [Collection Cluster info API](https://api.qdrant.tech/master/api-reference/distributed/collection-cluster-info).
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ weight: 3
|
||||
|
||||
## Configure Clusters
|
||||
|
||||
Next to the Hybrid Cloud specific scheduling options, you can change various advanced configuration options for your clusters. See [Configure Clusters](/documentation/cloud/configure-cluster/) for more details.
|
||||
Alongside Hybrid Cloud specific scheduling options, you can also adjust various other advanced configuration options for your clusters. See [Configure Clusters](/documentation/cloud/configure-cluster/) for more details.
|
||||
|
||||
## Scale Clusters
|
||||
|
||||
@@ -15,7 +15,7 @@ Hybrid cloud clusters can be scaled up and down, horizontall and vertically, at
|
||||
|
||||
### Automatic Shard Rebalancing
|
||||
|
||||
Qdrant Cloud supports automatic shard rebalancing when you scale your cluster horizontally. This ensures that the data is evenly distributed across the nodes, optimizing performance and resource utilization. For more details see [Shard Rebalancing](/documentation/cloud/configure-cluster/#shard-rebalancing).
|
||||
Qdrant Cloud supports automatic shard rebalancing when scaling your cluster horizontally. This ensures that data is evenly distributed across the nodes, optimizing performance and resource utilization. For more details see [Shard Rebalancing](/documentation/cloud/configure-cluster/#shard-rebalancing).
|
||||
|
||||
### Resharding
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ weight: 2
|
||||
|
||||
# Creating a Qdrant Cluster in Hybrid Cloud
|
||||
|
||||
Once you have created a Hybrid Cloud Environment, you can create a Qdrant cluster in that enviroment. Use the same process to [Create a cluster](/documentation/cloud/create-cluster/). This page also contains additional information on how to create a [production-ready cluster](/documentation/cloud/create-cluster/#creating-a-production-ready-cluster).
|
||||
Once a Hybrid Cloud Environment has been created you can follow the normal process to [create a Qdrant cluster](/documentation/cloud/create-cluster/) in that environment. This page also contains additional information on how to create a [production-ready cluster](/documentation/cloud/create-cluster/#creating-a-production-ready-cluster).
|
||||
|
||||
Make sure to select your Hybrid Cloud Environment as the target.
|
||||
|
||||
|
||||
@@ -394,7 +394,7 @@ spec:
|
||||
id: "a7d8d973-0cc5-42de-8d7b-c29d14d24840"
|
||||
version: "v1.15.1"
|
||||
size: 3
|
||||
rebalancestrategy: by_count_and_size
|
||||
rebalanceStrategy: by_count_and_size
|
||||
resources:
|
||||
cpu: 2
|
||||
memory: "8Gi"
|
||||
|
||||
Reference in New Issue
Block a user