yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-07-23 09:22:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenMetadata/openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md
Pere Miquel Brull 34fbe5d64c
Docs - Prepare 1.7 docs and 1.8 snapshot (#20882) 
* DOCS - Prepare 1.7 Release and 1.8 SNAPSHOT

* DOCS - Prepare 1.7 Release and 1.8 SNAPSHOT
2025-04-18 12:12:17 +05:30

1.6 KiB
Raw Permalink Blame History

title slug collate
Production-Ready Requirements for OpenMetadata Deployment /deployment/requirements false

Production-Ready Requirements for OpenMetadata Deployment

This section outlines the minimum hardware and resource specifications required for deploying OpenMetadata and its dependencies. These recommendations ensure optimal performance and scalability for your deployment.

OpenMetadata Server

  • vCPUs: Minimum of 2 vCPUs
  • Memory: 8 GiB
  • Storage Volume: 20 GiB (if using persistent volumes for logs)

External Services

OpenMetadata depends on the following external services, each with specific resource requirements:

Database (e.g., PostgreSQL)

  • vCPUs: Minimum of 2 vCPUs per instance
  • Memory: 8 GiB RAM per instance
  • Storage Volume:
    • 30 GiB (minimum)
    • Dynamic expansion up to 100 GiB

Elasticsearch

  • vCPUs: Minimum of 2 vCPUs per instance
  • Memory: 8 GiB RAM per instance
  • Storage Volume: 64 GiB

These specifications are also applicable for managed services like AWS RDS, GCP CloudSQL, or AWS OpenSearch.

Summary Recommendations

For a typical OpenMetadata deployment (one replica):

  • OpenMetadata Server: 2 vCPUs, 8 GiB RAM, 20 GiB persistent storage
  • Database: 2 vCPUs, 8 GiB RAM, 30 GiB storage (expandable to 100 GiB)
  • Elasticsearch: 2 vCPUs, 8 GiB RAM, 64 GiB storage

{%note%} Ensure these resources are allocated adequately to prevent performance bottlenecks or scalability issues. Managed services with equivalent specifications are supported. {%/note%}