From 5f528aa5da5be8418755692d75e8a5fbf08b3e80 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Fri, 3 Oct 2025 16:16:12 +0900 Subject: [PATCH 1/7] Clarify product environment minimum https://github.com/elastic/support-tech-lead/issues/1655 --- .../elastic-cloud/ec-customize-deployment-components.md | 4 ++-- .../elastic-cloud/elastic-cloud-hosted-planning.md | 9 +++++++++ .../monitor/stack-monitoring/ece-ech-stack-monitoring.md | 2 +- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index 012fa4f117..c6b688fda9 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -34,7 +34,7 @@ For trials, larger sizes are not available until you [add a credit card](../../c Currently, half the memory is assigned to the JVM heap (a bit less when monitoring is activated). For example, on a 32 GB cluster, 16 GB are allotted to heap. The disk-to-RAM ratio currently is 1:24, meaning that you get 24 GB of storage space for each 1 GB of RAM. All clusters are backed by SSD drives. ::::{tip} -For production systems, we recommend not using less than 4 GB of RAM for your cluster, which assigns 2 GB to the JVM heap. +For production systems, each Elasticsearch instance in your cluster should have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum Size Recommendations for Production Use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. :::: @@ -43,7 +43,7 @@ The CPU resources assigned to a cluster are relative to the size of your cluster If you don’t want to autoscale your deployment, you can manually increase or decrease capacity by adjusting the size of hot, warm, cold, and frozen [data tiers](../../../manage-data/lifecycle/data-tiers.md) nodes. For example, you might want to add warm tier nodes if you have time series data that is accessed less frequently and rarely needs to be updated. Alternatively, you might need cold tier nodes if you have time series data that is accessed occasionally and not normally updated. For clusters that have six or more {{es}} nodes, dedicated master-eligible nodes are introduced. When your cluster grows, it becomes important to consider separating dedicated master-eligible nodes from dedicated data nodes. ::::{tip} -We recommend using at least 4GB RAM for dedicated master nodes. +For clusters with dedicated master nodes, we advise using at least 4 GB of RAM for each dedicated master node. Review [Minimum Size Recommendations for Production Use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. :::: diff --git a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md index 0699e0867a..c49071d745 100644 --- a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md +++ b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md @@ -66,3 +66,12 @@ Scaling with {{ecloud}} is easy: * Or, if you prefer manual control, log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), select your deployment, select *Edit*, and either increase the number of zones or the size per zone. The recommendation is to scale up the resources within a single zone until the cluster can take the full load (add some buffer to be prepared for a peak of requests), then scale out by adding additional zones depending on your requirements: two zones for High Availability, three zones for Fault Tolerance. + +## Minimum Size Recommendations for Production Use [ec-minimum-recommendations] + +To ensure optimal performance and cluster stability in your production environment, we recommend adhering to the following minimum size guidelines. Deviating from these recommendations may lead to performance issues and cluster instability. For an enhanced user experience, consider planning your deployment capacity above these minimum recommendations, and adjust sizing based on your specific use case. + +* **{{es}} nodes / instances**: For production systems, each {{es}} node / instance in your cluster should have at least 4 GB of RAM. +* **Clusters with logs and monitoring enabled**: Enabling logs and monitoring requires additional resources. For production systems with these features enabled, we recommend allocating at least 4 GB of RAM per {{es}} node / instance. +* **Clusters with dedicated master nodes**: For clusters with dedicated master nodes, we advise using at least 4 GB of RAM for each dedicated master node. + diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index cf868d8d85..0f0bf0bc24 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -41,7 +41,7 @@ For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/aut ## Before you begin [logging-and-monitoring-limitations] * Some limitations apply when you use monitoring on ECH or ECE. To learn more, check the monitoring [restrictions and limitations](#restrictions-monitoring). -* Enabling logs and monitoring consumes extra resources on a deployment. For production systems, we recommend sizing deployments with logs and monitoring enabled to at least 4 GB of RAM on each {{es}} instance. +* Enabling logs and monitoring requires additional resources. For production systems with these features enabled, we recommend allocating at least 4 GB of RAM per {{es}} instance. Review [Minimum Size Recommendations for Production Use](../../deploy/elastic-cloud/elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. ## Monitoring for production use [logging-and-monitoring-production] From 58f8d8dc7a5daadc5e2989f872a7d026faf8c861 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Fri, 3 Oct 2025 16:20:15 +0900 Subject: [PATCH 2/7] Update elastic-cloud-hosted-planning.md use sentence case --- .../deploy/elastic-cloud/elastic-cloud-hosted-planning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md index c49071d745..cf47d24fee 100644 --- a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md +++ b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md @@ -67,7 +67,7 @@ Scaling with {{ecloud}} is easy: The recommendation is to scale up the resources within a single zone until the cluster can take the full load (add some buffer to be prepared for a peak of requests), then scale out by adding additional zones depending on your requirements: two zones for High Availability, three zones for Fault Tolerance. -## Minimum Size Recommendations for Production Use [ec-minimum-recommendations] +## Minimum size recommendations for production use [ec-minimum-recommendations] To ensure optimal performance and cluster stability in your production environment, we recommend adhering to the following minimum size guidelines. Deviating from these recommendations may lead to performance issues and cluster instability. For an enhanced user experience, consider planning your deployment capacity above these minimum recommendations, and adjust sizing based on your specific use case. From 2865e974f7c8ae229832d088dbcf08ed3613ec05 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Mon, 6 Oct 2025 09:21:53 +0900 Subject: [PATCH 3/7] Update deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md Co-authored-by: Vlada Chirmicci --- .../deploy/elastic-cloud/ec-customize-deployment-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index c6b688fda9..8874d5cc54 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -34,7 +34,7 @@ For trials, larger sizes are not available until you [add a credit card](../../c Currently, half the memory is assigned to the JVM heap (a bit less when monitoring is activated). For example, on a 32 GB cluster, 16 GB are allotted to heap. The disk-to-RAM ratio currently is 1:24, meaning that you get 24 GB of storage space for each 1 GB of RAM. All clusters are backed by SSD drives. ::::{tip} -For production systems, each Elasticsearch instance in your cluster should have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum Size Recommendations for Production Use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. +For production systems, each {{es}} instance in your cluster must have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. :::: From b31b171eca01ce5216ddcdbfbe1b3212cca4d572 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Mon, 6 Oct 2025 09:22:42 +0900 Subject: [PATCH 4/7] Update deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md Co-authored-by: Vlada Chirmicci --- .../deploy/elastic-cloud/ec-customize-deployment-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index 8874d5cc54..0e2aae7a04 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -43,7 +43,7 @@ The CPU resources assigned to a cluster are relative to the size of your cluster If you don’t want to autoscale your deployment, you can manually increase or decrease capacity by adjusting the size of hot, warm, cold, and frozen [data tiers](../../../manage-data/lifecycle/data-tiers.md) nodes. For example, you might want to add warm tier nodes if you have time series data that is accessed less frequently and rarely needs to be updated. Alternatively, you might need cold tier nodes if you have time series data that is accessed occasionally and not normally updated. For clusters that have six or more {{es}} nodes, dedicated master-eligible nodes are introduced. When your cluster grows, it becomes important to consider separating dedicated master-eligible nodes from dedicated data nodes. ::::{tip} -For clusters with dedicated master nodes, we advise using at least 4 GB of RAM for each dedicated master node. Review [Minimum Size Recommendations for Production Use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. +For clusters with dedicated master nodes, we recommend using at least 4 GB of RAM for each dedicated master node. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. :::: From af14d1d2395509ec3001c04bf72731200d4b1245 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Mon, 6 Oct 2025 09:23:01 +0900 Subject: [PATCH 5/7] Update deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md Co-authored-by: Vlada Chirmicci --- .../monitor/stack-monitoring/ece-ech-stack-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index 0f0bf0bc24..e95b492663 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -41,7 +41,7 @@ For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/aut ## Before you begin [logging-and-monitoring-limitations] * Some limitations apply when you use monitoring on ECH or ECE. To learn more, check the monitoring [restrictions and limitations](#restrictions-monitoring). -* Enabling logs and monitoring requires additional resources. For production systems with these features enabled, we recommend allocating at least 4 GB of RAM per {{es}} instance. Review [Minimum Size Recommendations for Production Use](../../deploy/elastic-cloud/elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. +* Enabling logs and monitoring requires additional resources. For production systems where these features are enabled, we recommend allocating at least 4 GB of RAM per {{es}} instance. Review [Minimum size recommendations for production use](../../deploy/elastic-cloud/elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. ## Monitoring for production use [logging-and-monitoring-production] From ff1aa9d661147ffe278695d3fe8d8c4707315b65 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Mon, 6 Oct 2025 09:32:50 +0900 Subject: [PATCH 6/7] revert the wording from "must" back to "should" I accidentally committed a suggestion but as I explained in https://github.com/elastic/docs-content/pull/3307#discussion_r2404747219, we'd better use "should" as our verbal to avoid strong obligation. --- .../deploy/elastic-cloud/ec-customize-deployment-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index 0e2aae7a04..0983a76cc9 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -34,7 +34,7 @@ For trials, larger sizes are not available until you [add a credit card](../../c Currently, half the memory is assigned to the JVM heap (a bit less when monitoring is activated). For example, on a 32 GB cluster, 16 GB are allotted to heap. The disk-to-RAM ratio currently is 1:24, meaning that you get 24 GB of storage space for each 1 GB of RAM. All clusters are backed by SSD drives. ::::{tip} -For production systems, each {{es}} instance in your cluster must have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. +For production systems, each {{es}} instance in your cluster should have at least 4 GB of RAM, which assigns 2 GB to the JVM heap. Review [Minimum size recommendations for production use](elastic-cloud-hosted-planning.md#ec-minimum-recommendations) for more details. :::: From cb85f3525587f83da6219c3dcc5137f3d46ef06f Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Mon, 6 Oct 2025 22:22:16 +0900 Subject: [PATCH 7/7] Update elastic-cloud-hosted-planning.md small tweak about wording per https://github.com/elastic/docs-content/pull/3307#discussion_r2405415674 --- .../deploy/elastic-cloud/elastic-cloud-hosted-planning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md index cf47d24fee..9db9e09cd3 100644 --- a/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md +++ b/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md @@ -71,7 +71,7 @@ The recommendation is to scale up the resources within a single zone until the c To ensure optimal performance and cluster stability in your production environment, we recommend adhering to the following minimum size guidelines. Deviating from these recommendations may lead to performance issues and cluster instability. For an enhanced user experience, consider planning your deployment capacity above these minimum recommendations, and adjust sizing based on your specific use case. -* **{{es}} nodes / instances**: For production systems, each {{es}} node / instance in your cluster should have at least 4 GB of RAM. +* **{{es}} nodes / instances**: For production systems, we recommend that each {{es}} node / instance in your cluster has at least 4 GB of RAM. * **Clusters with logs and monitoring enabled**: Enabling logs and monitoring requires additional resources. For production systems with these features enabled, we recommend allocating at least 4 GB of RAM per {{es}} node / instance. * **Clusters with dedicated master nodes**: For clusters with dedicated master nodes, we advise using at least 4 GB of RAM for each dedicated master node.