Skip to content

ECK: Document recovery from failed volume upsize #3694

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

ECK: Document recovery from failed volume upsize #3694

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
73c8586
wip
naemono Oct 13, 2025
d9ac2e5
Update wording.
naemono Oct 13, 2025
db5deaf
Fix the url
naemono Oct 13, 2025
9049817
Add missing .md
naemono Oct 14, 2025
337db62
Review changes
naemono Oct 15, 2025
6dc6eb7
Adjust wording for volume upsize errors
naemono Oct 28, 2025
344ca9c
Review comments
naemono Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions troubleshoot/deployments/cloud-on-k8s/common-problems.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -306,3 +306,14 @@ Check that the role mapping was deleted:
GET /_security/role_mapping/<roleName>
{}
```


## If a volume expansion failed [k8s-common-problems-volume-failed-expansion]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## If a volume expansion failed [k8s-common-problems-volume-failed-expansion]
## Volume expansion failed [k8s-common-problems-volume-failed-expansion]

The original is okay too, but this title format would be more consistent with our other troubleshooting topics, and most of the other ones on this page.


If you attempted an expansion of an {{es}} data 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. For example older versions of the Azure Disk CSI driver did not allow volume expansion without shutting down the Virtual Machine to which the volume was attached. If you try to adjust the volume claim template back to the original size you will encounter an error:

```
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 data to the new volumes, and will delete the old `StatefulSet` and its volumes once the operation is complete.