---
title: "Deployment FAQs"
description: "Looking for guidance on deploying Weaviate in a production environment? Whether you're scaling up from a proof-of-concept to an enterprise-wide implementation, migrating from another solution, or optimizing for specific workloads, you'll find practical answers to streamline your deployment process. Our goal is to help you achieve reliable performance, maintain data integrity, and minimize operational overhead as you harness the power of vector search for your applications!"
url: https://docs.weaviate.io/deploy/faqs
---

# Deployment FAQs

Looking for guidance on deploying Weaviate in a production environment? Whether you're scaling up from a proof-of-concept to an enterprise-wide implementation, migrating from another solution, or optimizing for specific workloads, you'll find practical answers to streamline your deployment process. Our goal is to help you achieve reliable performance, maintain data integrity, and minimize operational overhead as you harness the power of vector search for your applications!

#### Q1: Why did my cluster suddenly become read-only?

**Answer**

This almost always means you've run out of disk space. Weaviate protects itself by switching to read-only mode when disk usage exceeds a configured threshold. You'll need to increase the disk size available to Weaviate. From `v1.36.0` on, the shards become writable again automatically. On earlier versions, you also need to reset the read-only status. See [disk pressure warnings and limits](https://docs.weaviate.io/deploy/configuration/persistence#disk-pressure-warnings-and-limits).

#### Q2: How do I deploy Weaviate using AWS Marketplace?

**Answer**

This [page](https://docs.weaviate.io/deploy/installation-guides/aws-marketplace) will walk you through all the necessary steps to deploy Weaviate using AWS marketplace.

#### Q3: How do I deploy Weaviate using GCP Marketplace?

**Answer**

This [page](https://docs.weaviate.io/deploy/installation-guides/gcp-marketplace) will walk you through all the necessary steps to deploy Weaviate using GCP marketplace.

#### Q4: How do I run Weaviate as a managed service on DigitalOcean?

**Answer**

This [page](https://docs.weaviate.io/deploy/installation-guides/digitalocean) will walk you through running Weaviate as a fully managed service operated by DigitalOcean.

#### Q5: Is there a recommended limit for collections?

**Answer**

If you plan to create more than **20** collections, you may want to consider multi-tenancy instead for better scaling and performance.

**Additional information:** [Scaling limits with collections](https://docs.weaviate.io/weaviate/starter-guides/managing-collections/collections-scaling-limits)

#### Q6: What are some common issues that occur during deployment?

**Answer**

Common issues that occur during deployment include:

- The cluster becoming `read-only`.
- Query results being inconsistent.
- Nodes unable to maintain consensus.
- Creating too many collections.

#### Further resources

For further information, the [troubleshooting page](https://docs.weaviate.io/deploy/faqs/troubleshooting) will help with some of the common issue encountered.

#### Q7: What's the difference between Weaviate and other databases?

**Answer**

Weaviate has complex processes which means that ingestion and deletion require more steps than other types of databases. Data ingestion tends to take longer than a traditional database because of vectorization and deleting objects can be expensive due to the embedding costs.

#### Q8: Do my resources free up immediately after deleting objects?

**Answer**

No, it does not happen instantaneously. When you delete objects a tombstone is created. The data removal and index cleanup occur as background processes.

#### Q9: What's the difference between client timeouts and module timeouts?

**Answer**

- **Client timeout:** These are timeouts between the client and Weaviate server.

- **Module timeout:** These are timeouts that occurs when Weaviate interacts with external modules like LLMs and vectorizers.