Database persistent volume is filling
Symptom
A CustomerDatabasePersistentVolumeFillingUp alert is firing.
CustomerDatabasePersistentVolumeFillingUp alerts are sent to subscribers via email.
|
Observations
Here are the details on the alerts:
Alert: CustomerDatabasePersistentVolumeFillingUp
Expression |
|
Delay |
|
Labels |
|
Annotations |
|
Determine current size of database persistent volume
The name of the database persistent volume claim and its namespace are contained in the alert, for example "database-prod-magnolia-helm-public-db-0".
You can find the details on the persistent volume by displaying the persistent volume claim using kubectl:
kubectl -n <namespace from alert> get pvc <persistent volume claim from alert>Executing the above will list the size of the persistent volume shown in the CAPACITY column.
$ kubectl -n prod get pvc database-prod-magnolia-helm-public-db-0
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
database-prod-magnolia-helm-public-db-0 Bound pvc-e695274c-5794-4a78-afe0-e86b0efd40ed 10Gi RWO local-path 9dSolutions
This section provides solutions that should help resolve the issue in most cases.
Increase the capacity of the database persistent volume
The space allocated to the Database persistent volume can be increased with a "hot fix" or by modifying the values of the Helm chart deploying Magnolia.
You can edit the persistent volume claim and increase the capacity in Rancher or with kubectl.
Edit the persistent volume claim or the persistent volume associated with the claim and increase the size of the storage resource.
resources:
requests:
storage: 10Gi (1)| 1 | Increase the storage property.
|