From 196bfaae6ba5d6bf19c1f5e876d1f23d63fa09cf Mon Sep 17 00:00:00 2001 From: Rounak Dhillon <162090200+RounakDhillon@users.noreply.github.com> Date: Wed, 23 Jul 2025 11:16:51 +0530 Subject: [PATCH] Docs: Minumum Requirement Correction for OpenMetadata (#22521) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”> --- .../production-ready-requirements.md | 18 +++++++++--------- .../production-ready-requirements.md | 18 +++++++++--------- .../production-ready-requirements.md | 18 +++++++++--------- 3 files changed, 27 insertions(+), 27 deletions(-) diff --git a/openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md b/openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md index 8477b5fb827..e37f5f7177f 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md +++ b/openmetadata-docs/content/v1.7.x/deployment/production-ready-requirements.md @@ -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. diff --git a/openmetadata-docs/content/v1.8.x/deployment/production-ready-requirements.md b/openmetadata-docs/content/v1.8.x/deployment/production-ready-requirements.md index 8477b5fb827..e37f5f7177f 100644 --- a/openmetadata-docs/content/v1.8.x/deployment/production-ready-requirements.md +++ b/openmetadata-docs/content/v1.8.x/deployment/production-ready-requirements.md @@ -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. diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/production-ready-requirements.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/production-ready-requirements.md index 8477b5fb827..e37f5f7177f 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/production-ready-requirements.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/production-ready-requirements.md @@ -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.