ComputeStacks offers multiple ways to restrict resource consumption by individual containers.
CPU, Memory, and Swap usage can be limited by defining those values within the container package.
Please note: You may only limit disk IO, not usage.
Availability Zone Container Restrictions¶
|OOM Killer|| ||Enable or Disable the OOM Killer for containers. If disabled, a container may become hung and require manual intervention.|
|PID Limit|| ||Maximum number of active processes allowed inside a container.|
|Max Open Files (Soft)|| ||Soft limit for maximum allowed open files within a container.|
|Max Open Files (Hard)|| ||Hard limit for maximum allowed open files within a container.|
Node Container Restrictions¶
In order for these settings to be applied, you must define the
block device path on the node. This should be set to where
/var/lib/docker is mounted. Examples include:
Incorrect setting will prevent the container from starting.
|Write Bytes Per Second|| ||Maximum allowed Bytes Per Second written to disk, per container.|
|Write Operations Per Second|| ||Maximum allowed Operations Per Second (IOPS) written to disk, per container.|
|Read Bytes Per Second|| ||Maximum allowed Bytes Per Second read from disk, per container.|
|Read Operations Per Second|| ||Maximum allowed Operations Per Second (IOPS) read from disk, per container.|