GitHub user bhouse-nexthop created a discussion: Disable cluster.memory.allocated.capacity.disablethreshold check? Bad interaction with mem.overprovisioning.factor
I am running Cloudstack 4.22.0.0 + PR #11932. I have these configurations set: * mem.overprovisioning.factor: 4 * cluster.memory.allocated.capacity.disablethreshold: 0.85 * vm.min.memory.equals.memory.divided.by.mem.overprovisioning.factor: false Allocated capacity looks like this: <img width="367" height="123" alt="image" src="https://github.com/user-attachments/assets/3b945534-9f95-4c2e-a40f-2ed41f607506"; /> But actual memory usage looks like this: <img width="778" height="231" alt="image" src="https://github.com/user-attachments/assets/140aee51-ac50-4169-b5ef-9ed19cc7f841"; /> This proves the PR #11932 + the fact that I tuned KSM on the host is working nicely. That said, with cluster.memory.allocated.capacity.disablethreshold at 85%, I get: ``` 2025-12-18 22:35:07,143 WARN [c.c.d.FirstFitPlanner] (API-Job-Executor-67:[ctx-c19a2c63, job-23855, ctx-d91b5367]) (logid:8ecbd546) Cannot allocate cluster list [1] for VM creation since their allocated percentage crosses the disable capacity threshold defined at each cluster at Global Settings Configuration [name: cluster.memory.allocated.capacity.disablethreshold, value: 0.85] for capacity Type : MEMORY, skipping these clusters ``` I tried setting the value to 0 thinking that means disable (not sure why you'd ever use a value of 0 as that would make it always fail), but it didn't fix the error. I currently have it set to 1 for 100% but I have a feeling in a few days I'm going to hit the same error again even though I haven't hit my overprovision ratio. Either this check needs to have the ability to be completely disabled, or it needs to be made to honor the overprovisioning factor. Anyone have any guidance on this? GitHub link: https://github.com/apache/cloudstack/discussions/12301 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
