You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-arc/data/resize-persistent-volume-claim.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,20 +18,20 @@ This article explains how to resize an existing persistent volume to increase it
18
18
> [!NOTE]
19
19
> Resizing PVCs using this method only works your `StorageClass` supports `AllowVolumeExpansion=True`.
20
20
21
-
When you deploy an Azure Arc enabled SQL managed instance, you can configure the size of the persistent volume (PV) for `data`, `logs`, `datalogs`, and `backups`. The deployment creates these volumes based on the values set by parameters `--volume-size-data`, `--volume-size-logs`, `--volume-size-datalogs`, and `--volume-size-backups`. When these volumes become full, you will need to resize the `PersistentVolumes`. Azure Arc enabled SQL Managed Instance is deployed as part of a `Statefulsets` for both General Purpose or Business Critical service tiers. Kubernetes supports automatic resizing for persistent volumes but not for volumes attached to `StatefulSets`.
21
+
When you deploy an Azure Arc enabled SQL managed instance, you can configure the size of the persistent volume (PV) for `data`, `logs`, `datalogs`, and `backups`. The deployment creates these volumes based on the values set by parameters `--volume-size-data`, `--volume-size-logs`, `--volume-size-datalogs`, and `--volume-size-backups`. When these volumes become full, you will need to resize the `PersistentVolumes`. Azure Arc enabled SQL Managed Instance is deployed as part of a `StatefulSet` for both General Purpose or Business Critical service tiers. Kubernetes supports automatic resizing for persistent volumes but not for volumes attached to `StatefulSet`.
22
22
23
-
Following are the steps to resize persistent volumes attached to `StatefulSets`:
23
+
Following are the steps to resize persistent volumes attached to `StatefulSet`:
24
24
25
-
1. Scale the `StatefulSets` replicas to 0
25
+
1. Scale the `StatefulSet` replicas to 0
26
26
2. Patch the PVC to the new size
27
-
3. Scale the `StatefulSets` replicas back to the original size
27
+
3. Scale the `StatefulSet` replicas back to the original size
28
28
29
29
During the patching of `PersistentVolumeClaim`, the status of the persistent volume claim will likely change from: `Attached` to `Resizing` to `FileSystemResizePending` to `Attached`. The exact states will depend on the storage provisioner.
30
30
31
31
> [Note]
32
32
> Ensure the managed instance is in a healthy state before you proceed. Run `kubectl get sqlmi -n <namespace>` and check the status of the managed instance.
33
33
34
-
## 1. Scale the `StatefulSets` replicas to 0
34
+
## 1. Scale the `StatefulSet` replicas to 0
35
35
36
36
There is one `StatefulSet` deployed for each Arc SQL MI. The number of replicas in the `StatefulSet` is equal to the number of replicas in the Arc SQL MI. For General Purpose service tier, this is 1. For Business Critical service tier it could be 1, 2 or 3 depending on how many replicas were specified. Run the below command to get the number of `StatefulSet` replicas if you have a Business Critical instance.
37
37
@@ -47,7 +47,7 @@ kubectl get sts --namespace arc
47
47
48
48
Notice the number of stateful sets under the `READY` column for the SQL managed instance(s).
49
49
50
-
Run the below command to scale the `StatefulSets` replicas to 0:
50
+
Run the below command to scale the `StatefulSet` replicas to 0:
0 commit comments