yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-07-25 18:30:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Minumum Requirement Correction for OpenMetadata (#22521)

Browse Source 
Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”>
This commit is contained in:
Rounak Dhillon 2025-07-23 11:16:51 +05:30 committed by GitHub
parent bc9075f59d
commit 196bfaae6b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 27 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md
View File

@ -9,16 +9,16 @@ collate: false
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)
- **vCPUs**: Minimum of 4 vCPUs
- **Memory**: 16 GiB
- **Storage Volume**: 100 GiB
## 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
- **vCPUs**: Minimum of 4 vCPUs per instance
- **Memory**: 16 GiB RAM per instance
- **Storage Volume**:
- 30 GiB (minimum)
- Dynamic expansion up to 100 GiB
@ -26,15 +26,15 @@ OpenMetadata depends on the following external services, each with specific reso
### Elasticsearch
- **vCPUs**: Minimum of 2 vCPUs per instance
- **Memory**: 8 GiB RAM per instance
- **Storage Volume**: 64 GiB
- **Storage Volume**: 100 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
- **OpenMetadata Server**: 4 vCPUs, 16 GiB RAM, 100 GiB persistent storage
- **Database**: 4 vCPUs, 16 GiB RAM, 30 GiB storage (expandable to 100 GiB)
- **Elasticsearch**: 2 vCPUs, 8 GiB RAM, 100 GiB storage
{%note%}
Ensure these resources are allocated adequately to prevent performance bottlenecks or scalability issues. Managed services with equivalent specifications are supported.

18
openmetadata-docs/content/v1.8.x/deployment/production-ready-requirements.md
View File

@ -9,16 +9,16 @@ collate: false
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)
- **vCPUs**: Minimum of 4 vCPUs
- **Memory**: 16 GiB
- **Storage Volume**: 100 GiB
## 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
- **vCPUs**: Minimum of 4 vCPUs per instance
- **Memory**: 16 GiB RAM per instance
- **Storage Volume**:
- 30 GiB (minimum)
- Dynamic expansion up to 100 GiB
@ -26,15 +26,15 @@ OpenMetadata depends on the following external services, each with specific reso
### Elasticsearch
- **vCPUs**: Minimum of 2 vCPUs per instance
- **Memory**: 8 GiB RAM per instance
- **Storage Volume**: 64 GiB
- **Storage Volume**: 100 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
- **OpenMetadata Server**: 4 vCPUs, 16 GiB RAM, 100 GiB persistent storage
- **Database**: 4 vCPUs, 16 GiB RAM, 30 GiB storage (expandable to 100 GiB)
- **Elasticsearch**: 2 vCPUs, 8 GiB RAM, 100 GiB storage
{%note%}
Ensure these resources are allocated adequately to prevent performance bottlenecks or scalability issues. Managed services with equivalent specifications are supported.

18
openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/production-ready-requirements.md
View File

@ -9,16 +9,16 @@ collate: false
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)
- **vCPUs**: Minimum of 4 vCPUs
- **Memory**: 16 GiB
- **Storage Volume**: 100 GiB
## 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
- **vCPUs**: Minimum of 4 vCPUs per instance
- **Memory**: 16 GiB RAM per instance
- **Storage Volume**:
- 30 GiB (minimum)
- Dynamic expansion up to 100 GiB
@ -26,15 +26,15 @@ OpenMetadata depends on the following external services, each with specific reso
### Elasticsearch
- **vCPUs**: Minimum of 2 vCPUs per instance
- **Memory**: 8 GiB RAM per instance
- **Storage Volume**: 64 GiB
- **Storage Volume**: 100 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
- **OpenMetadata Server**: 4 vCPUs, 16 GiB RAM, 100 GiB persistent storage
- **Database**: 4 vCPUs, 16 GiB RAM, 30 GiB storage (expandable to 100 GiB)
- **Elasticsearch**: 2 vCPUs, 8 GiB RAM, 100 GiB storage
{%note%}
Ensure these resources are allocated adequately to prevent performance bottlenecks or scalability issues. Managed services with equivalent specifications are supported.