[PR #2] High RAM usage shouldn't terminate script #23

Closed
opened 2026-02-26 17:46:10 +03:00 by kerem · 0 comments
Owner

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_verification slightly to return a status on a recoverable failure. The main loop then sees the low-memory condition as something it can try again later.

**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_verification` slightly to return a status on a recoverable failure. The main loop then sees the low-memory condition as something it can try again later.
kerem 2026-02-26 17:46:10 +03:00
kerem changed title from [PR #2] [MERGED] High RAM usage shouldn't terminate script to [PR #2] High RAM usage shouldn't terminate script 2026-03-01 15:58:45 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxmox-load-balancer#23
No description provided.