mirror of
https://github.com/cvk98/Proxmox-load-balancer.git
synced 2026-04-25 04:25:50 +03:00
[PR #2] High RAM usage shouldn't terminate script #23
Labels
No labels
documentation
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxmox-load-balancer#23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Original Pull Request: https://github.com/cvk98/Proxmox-load-balancer/pull/2
State: closed
Merged: Yes
Sometimes, I have a short-term situation on my cluster where I spin up a lot of VMs for a while, causing high memory utilisation. As this condition goes away once those VMs are destroyed, I don't think a high-RAM condition should permanently kill the load-balancer.
I've modified the
cluster_load_verificationslightly to return a status on a recoverable failure. The main loop then sees the low-memory condition as something it can try again later.[PR #2] [MERGED] High RAM usage shouldn't terminate scriptto [PR #2] High RAM usage shouldn't terminate script