Em Sharnoff 2cf6a47cca vm-monitor: Deny not fail downscale if no memory stats yet (#5606) ...

Fixes an issue we observed on staging that happens when the
autoscaler-agent attempts to immediately downscale the VM after binding,
which is typical for pooled computes.

The issue was occurring because the autoscaler-agent was requesting
downscaling before the vm-monitor had gathered sufficient cgroup memory
stats to be confident in approving it. When the vm-monitor returned an
internal error instead of denying downscaling, the autoscaler-agent
retried the connection and immediately hit the same issue (in part
because cgroup stats are collected per-connection, rather than
globally).

2023-10-19 19:09:37 +01:00

..

bin

compute_ctl: add vm-monitor (#4946)

2023-08-24 15:54:37 -04:00

cgroup.rs

vm-monitor: Switch from memory.high to polling memory.stat (#5524)

2023-10-17 15:30:40 -07:00

dispatcher.rs

vm-monitor: Switch from memory.high to polling memory.stat (#5524)

2023-10-17 15:30:40 -07:00

filecache.rs

vm-monitor: Add flag for when file cache on disk (#5130)

2023-08-29 12:44:48 -07:00

lib.rs

vm-monitor: Don't include Args in top-level span (#5264)

2023-09-10 20:15:53 +03:00

protocol.rs

monitor/compute_ctl: remove references to the informant (#5115)

2023-08-29 02:59:27 +03:00

runner.rs

vm-monitor: Deny not fail downscale if no memory stats yet (#5606)

2023-10-19 19:09:37 +01:00