From 1e7182e3927db738dea16d5b6e46310e880c6a75 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 28 May 2025 15:55:59 +0200 Subject: [PATCH 1/3] ece hard limit and podman introduction --- .../cloud-enterprise/resource-overrides.md | 34 ++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md index c9298075c..e17f49ae0 100644 --- a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md +++ b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md @@ -10,7 +10,9 @@ products: # Resource overrides [ece-resource-overrides] -{{ecloud}} allocators assign resources to {{es}} instances based on RAM, where RAM is proportional to CPU and disk resources. As needed, you can temporarily override the allocated resources to stabilize the deployment. You should reset overrides as soon as possible, or make the override permanent by [changing your configuration](working-with-deployments.md). +{{ecloud}} allocators assign resources to {{es}} instances based on RAM, where RAM is proportional to CPU and disk resources. As needed, you can temporarily override the allocated resources to stabilize the deployment. To do this, use the contextual menu available on each instance in the deployment UI. + +Overrides are intended to be temporary and may be lost after making configuration changes to the deployment. You should reset overrides as soon as possible, or make them permanent by [changing your configuration](./configure-deployment.md). The RAM to CPU proportions can’t be overridden per instance. @@ -31,3 +33,33 @@ Overriding the instance size restarts the {{es}} node. :::: When an instance within a deployment has resource overrides, it displays a warning banner reading **Elastic added temporary capacity to stabilize the deployment**. [Configuration changes](working-with-deployments.md) can still be safely submitted. + +## Disabling CPU quotas at deployment level [cpu-hard-limit] + +In addition to overriding resources for individual instances, you can also completely disable CPU limits for your deployment from the **Operations** section of the deployment UI. + +::::{note} +When running ECE on Podman, CPU quotas for existing instances cannot be removed or updated. As a result, disabling the CPU hard limit has no effect on Podman-based allocators. +:::: + +::::{important} +Disabling the CPU hard limit for an entire deployment is an advanced action and should be approached with caution. This setting removes CPU quotas from the containers, which means some instances could consume excessive CPU resources and degrade the performance of other instances running on the same allocators. + +We strongly recommend making this change only under the guidance of Elastic Support, and only as a temporary measure or for troubleshooting purposes. +:::: + +To disable CPU limits of your deployment instances, choose one of the following methods: + +* Open the **Operations** page of the deployment UI, and select **Turn off** in the `CPU hard limit` section. + +* Use the [advanced editor](./advanced-cluster-configuration.md), and in the **{{es}} cluster data** section, look for the : + + ```yaml + "resources": { + "cpu": { + "hard_limit": false + } + } + ``` + +This change doesn’t require a restart of the deployment. \ No newline at end of file From c331e2743c99ba39618ec1bfe003c3d33165feab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Thu, 29 May 2025 08:09:11 +0200 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/deploy/cloud-enterprise/resource-overrides.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md index e17f49ae0..2b177af25 100644 --- a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md +++ b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md @@ -50,9 +50,9 @@ We strongly recommend making this change only under the guidance of Elastic Supp To disable CPU limits of your deployment instances, choose one of the following methods: -* Open the **Operations** page of the deployment UI, and select **Turn off** in the `CPU hard limit` section. +* Open the **Operations** page of the deployment UI, and select **Turn off** in the **CPU hard limit** section. -* Use the [advanced editor](./advanced-cluster-configuration.md), and in the **{{es}} cluster data** section, look for the : +* Use the [advanced editor](./advanced-cluster-configuration.md), and in the **{{es}} cluster data** section, look for the following setting: ```yaml "resources": { From 0132439cdba3427d549b37ca9cb2e0b1cbdb2c8f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 3 Jun 2025 09:30:30 +0200 Subject: [PATCH 3/3] operations UI access and advanced editor refined --- deploy-manage/deploy/cloud-enterprise/resource-overrides.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md index 2b177af25..796cd9628 100644 --- a/deploy-manage/deploy/cloud-enterprise/resource-overrides.md +++ b/deploy-manage/deploy/cloud-enterprise/resource-overrides.md @@ -36,7 +36,7 @@ When an instance within a deployment has resource overrides, it displays a warni ## Disabling CPU quotas at deployment level [cpu-hard-limit] -In addition to overriding resources for individual instances, you can also completely disable CPU limits for your deployment from the **Operations** section of the deployment UI. +In addition to overriding resources for individual instances, you can also completely disable CPU limits for your deployment from the **Operations** page of each deployment. ::::{note} When running ECE on Podman, CPU quotas for existing instances cannot be removed or updated. As a result, disabling the CPU hard limit has no effect on Podman-based allocators. @@ -62,4 +62,6 @@ To disable CPU limits of your deployment instances, choose one of the following } ``` + Set `hard_limit` to `false` to disable CPU limits, or to `true` to enforce strict CPU limits (default behavior). + This change doesn’t require a restart of the deployment. \ No newline at end of file