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
What steps did you take and what happened:
It appears that when an issue occurs, JIVA remounts the volume, but does not remove a stale mount point, resulting in high IO latency.
What did you expect to happen:
Jiva to cleanup stale mount points periodically.
Anything else you would like to add:
Here are a list of mount points which are not cleaned up causing high load averages; and terrible performance for this storage solution.
Environment: K3s
Jiva version: v3.1.0
OpenEBS version: v3.1.0
Kubernetes version (use kubectl version): v1.23.4+k3s1
Kubernetes installer & version: v1.23.4+k3s1
Cloud provider or hardware configuration: AMD Ryzen servers, 64 to 128GB ram, 3 nodes
OS (e.g. from /etc/os-release): Ubuntu
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
It appears that when an issue occurs, JIVA remounts the volume, but does not remove a stale mount point, resulting in high IO latency.
What did you expect to happen:
Jiva to cleanup stale mount points periodically.
Anything else you would like to add:
Here are a list of mount points which are not cleaned up causing high load averages; and terrible performance for this storage solution.
Environment: K3s
kubectl version
): v1.23.4+k3s1/etc/os-release
): UbuntuThe text was updated successfully, but these errors were encountered: