From b7b6d966a8e140e0cba7c5076d66378611bfd249 Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Mon, 13 Oct 2025 13:46:01 -0500 Subject: [PATCH 1/5] wip Signed-off-by: Michael Montgomery --- .../deployments/cloud-on-k8s/common-problems.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index 7359f9108f..a6a5fe829c 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -306,3 +306,14 @@ Check that the role mapping was deleted: GET /_security/role_mapping/ {} ``` + + +## If a volume expansion failed [k8s-common-problems-volume-failed-expansion] + +If you attempted an expansion of an Elasticsearch volume via its volume claim template, you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. To troubleshoot, refer to the official documentation at https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update. If you try to adjust the volume claim template back to the original size you will encounter a failure + +``` +Failed to apply spec change: handle volume expansion: decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data +``` + +In this scenario the best course of action is to rename the existing `nodeSet` to a new name while simultaneously updating the volume claim template to the original size. From 30e8b124b037a6f30d6f8df7b2008ba770d57041 Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Mon, 13 Oct 2025 14:10:42 -0500 Subject: [PATCH 2/5] Update wording. Signed-off-by: Michael Montgomery --- troubleshoot/deployments/cloud-on-k8s/common-problems.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index a6a5fe829c..0798c37cb7 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -310,10 +310,10 @@ GET /_security/role_mapping/ ## If a volume expansion failed [k8s-common-problems-volume-failed-expansion] -If you attempted an expansion of an Elasticsearch volume via its volume claim template, you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. To troubleshoot, refer to the official documentation at https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update. If you try to adjust the volume claim template back to the original size you will encounter a failure +If you attempted an expansion of an Elasticsearch volume via its (volume claim template)[/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update], you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: ``` Failed to apply spec change: handle volume expansion: decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data ``` -In this scenario the best course of action is to rename the existing `nodeSet` to a new name while simultaneously updating the volume claim template to the original size. +In this scenario the best course of action is to rename the existing `nodeSet` to a new name while simultaneously updating the volume claim template to the original size. This operation will bring a new `StatefulSet` online while moving all existing indices to the new volumes and will delete the old `StatefulSet` and its volumes once the operation is complete. From 382e9072ef0e4b219e19e8c315bce9e35d04c0d2 Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Mon, 13 Oct 2025 14:20:46 -0500 Subject: [PATCH 3/5] Fix the url Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- troubleshoot/deployments/cloud-on-k8s/common-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index 0798c37cb7..da95ece6c0 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -310,7 +310,7 @@ GET /_security/role_mapping/ ## If a volume expansion failed [k8s-common-problems-volume-failed-expansion] -If you attempted an expansion of an Elasticsearch volume via its (volume claim template)[/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update], you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: +If you attempted an expansion of an Elasticsearch volume via its [volume claim template](/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update), you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: ``` Failed to apply spec change: handle volume expansion: decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data From 9467f5320f76d3995dcd5e560b57e843503f44cf Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Tue, 14 Oct 2025 09:31:53 -0500 Subject: [PATCH 4/5] Add missing .md Signed-off-by: Michael Montgomery --- troubleshoot/deployments/cloud-on-k8s/common-problems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index da95ece6c0..0b97eb824b 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -310,7 +310,7 @@ GET /_security/role_mapping/ ## If a volume expansion failed [k8s-common-problems-volume-failed-expansion] -If you attempted an expansion of an Elasticsearch volume via its [volume claim template](/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates#k8s-volume-claim-templates-update), you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: +If you attempted an expansion of an Elasticsearch volume via its [volume claim template](/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates.md#k8s-volume-claim-templates-update), you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: ``` Failed to apply spec change: handle volume expansion: decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data From 5457e10c32564016b48d61e9c82b177fab0796ab Mon Sep 17 00:00:00 2001 From: Michael Montgomery Date: Wed, 15 Oct 2025 07:25:37 -0500 Subject: [PATCH 5/5] Review changes Signed-off-by: Michael Montgomery --- troubleshoot/deployments/cloud-on-k8s/common-problems.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index 0b97eb824b..41a7de6f5e 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -310,10 +310,10 @@ GET /_security/role_mapping/ ## If a volume expansion failed [k8s-common-problems-volume-failed-expansion] -If you attempted an expansion of an Elasticsearch volume via its [volume claim template](/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates.md#k8s-volume-claim-templates-update), you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: +If you attempted an expansion of an {{es}} volume via its [volume claim template](/deploy-manage/deploy/cloud-on-k8s/volume-claim-templates.md#k8s-volume-claim-templates-update), you may have encountered scenarios where the operation failed such as Azure not allowing volume expansion without shutting down the Virtual Machine to which it is attached. If you try to adjust the volume claim template back to the original size you will encounter a failure: ``` Failed to apply spec change: handle volume expansion: decreasing storage size is not supported: an attempt was made to decrease storage size for claim elasticsearch-data ``` -In this scenario the best course of action is to rename the existing `nodeSet` to a new name while simultaneously updating the volume claim template to the original size. This operation will bring a new `StatefulSet` online while moving all existing indices to the new volumes and will delete the old `StatefulSet` and its volumes once the operation is complete. +In this scenario the best course of action is to rename the existing `nodeSet` to a new name while simultaneously updating the volume claim template to the original size. This operation will bring a new `StatefulSet` online while moving all existing indices to the new volumes, and will delete the old `StatefulSet` and its volumes once the operation is complete.