docs(#2754): document the container weights in coordinator/security/persistence
The PR added CPUWeight=/IOWeight= to the drop-in but left the prose docs describing a two-setting file. Covers the cap-vs-share distinction, the hive-wide-only scope (no resource-limits.json override), and the iocost/BFQ caveat that makes IOWeight= inert on most hosts.
This commit is contained in:
parent
35d9d79912
commit
f28a1e33d3
3 changed files with 30 additions and 2 deletions
|
|
@ -318,7 +318,9 @@ Contents:
|
|||
an absent file, absent agent, or absent field falls back to the
|
||||
hive-wide `services.hyperhive.agentCpuQuota` / `agentMemoryMax`,
|
||||
so an agent can override only its memory and still track the hive
|
||||
default for CPU.
|
||||
default for CPU. The `CPUWeight=` / `IOWeight=` shares in the same
|
||||
drop-in have **no** per-agent override — they are hive-wide only and
|
||||
come straight off `HiveEnv`, so this file has no field for them.
|
||||
|
||||
The root agent has the meta dir RO-mounted at `/meta/`.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue