subset
access
required: false
scopable: true
candidates: rwo, roo, rwx, rox
default: rwo
The access mode of the volume.
rwo
is Read Write Onceroo
is Read Only Oncerwx
is Read Write Manyrox
is Read Only Many
rox
and rwx
modes are served by flex volume services.
comment
required: false
scopable: false
Comments help the users understand the role of the object and its resources.
parallel
required: false
scopable: true
convert: bool
If set to true
, actions are executed in parallel on the resource of this subset.
For example, a service with:
[app#1]
start = /bin/true
[app#2]
start = /bin/true
[app#3]
start = /bin/true
subset = workers
[app#4]
start = /bin/true
subset = workers
[subset#app:workers]
parallel = true
Would have a start sequence like:
app#1 ---> app#2 -+-> app#3
`-> app#4
pg_blkio_weight
required: false
scopable: true
Example:
pg_blkio_weight = 50
Block IO relative weight. Value: between 10
and 1000
.
The kernel default is 1000
.
pg_cpu_quota
required: false
scopable: true
Example:
pg_cpu_quota = 50%@all
The kernel default value is used, which usually is 1024 shares.
In a cpu-bound situation, this setting ensures the service does not use more than its share of cpu resource. The actual percentile depends on shares allowed to other services.
pg_cpu_shares
required: false
scopable: true
convert: size
Example:
pg_cpu_shares = 512
The kernel default value is used, which usually is 1024 shares.
In a cpu-bound situation, this setting ensures the service does not use more than its share of cpu resource. The actual percentile depends on shares allowed to other services.
pg_cpus
required: false
scopable: true
depends: create_pg=true
Example:
pg_cpus = 0-2
Allow service process to bind only the specified cpus.
Cpus are specified as list or range : 0,1,2
or 0-2
.
pg_mem_limit
required: false
scopable: true
convert: size
Example:
pg_mem_limit = 512m
Ensures the service does not use more than specified memory (in bytes).
The Out-Of-Memory killer is triggered in case of tresspassing.
pg_mem_oom_control
required: false
scopable: true
Example:
pg_mem_oom_control = 1
A flag (0 or 1) that enables or disables the Out of Memory killer for the processes of the group.
- If enabled (0), tasks that attempt to consume more memory than they are allowed are immediately killed by the OOM killer.
- If disabled (1), tasks are allowed to continue to try allocating memory, stressing the system.
The OOM killer is enabled by default in every cgroup using the memory controller.
pg_mem_swappiness
required: false
scopable: true
Example:
pg_mem_swappiness = 40
Set a swappiness percentile value for the process group.
pg_mems
required: false
scopable: true
Example:
pg_mems = 0-2
Allow service process to bind only the specified memory nodes.
Memory nodes are specified as list or range : 0,1,2
or 0-2
.
pg_vmem_limit
required: false
scopable: true
convert: size
Example:
pg_vmem_limit = 1g
Ensures the service does not use more than specified memory+swap (in bytes).
The Out-Of-Memory killer is triggered in case of tresspassing.
The specified value must be greater than pg_mem_limit
.
pool
required: false
scopable: true
The name of the pool this volume was allocated from.
provision_timeout
required: false
scopable: true
convert: duration
Example:
provision_timeout = 1m30s
Wait for <duration>
before declaring the action a failure.
Takes precedence over timeout
.
size
required: false
scopable: true
convert: size
The size used by this volume in its pool.
start_timeout
required: false
scopable: true
convert: duration
Example:
start_timeout = 1m30s
Wait for <duration>
before declaring the action a failure.
Takes precedence over timeout
.
stat_timeout
required: false
scopable: true
convert: duration
The fs resources status evaluation includes a stat syscall test. This keyword defines the maximum wait time for those stat calls to respond.
When expired, the resource status is degraded is to warn, which can trigger a monitor action (reboot or crash the node) if the resource is monitored.
status_timeout
required: false
scopable: true
default: 1m
convert: duration
Example:
status_timeout = 10s
The maximum duration of the instance status evaluation.
For example, the total start action duration is constrained by different timeouts:
-
the
start_timeout
Limiting the start action duration. -
the
stop_timeout
Limiting the start rollback duration triggered by start errors. -
the
status_timeout
Limiting the post-start instance status evaluation duration.
stop_timeout
required: false
scopable: true
convert: duration
Example:
stop_timeout = 1m30s
Wait for <duration>
before declaring the action a failure.
Takes precedence over timeout
.
sync_timeout
required: false
scopable: true
convert: duration
Example:
sync_timeout = 1m30s
Wait for <duration>
before declaring the action a failure.
Takes precedence over timeout
.
timeout
required: false
scopable: true
default: 1h
convert: duration
Example:
timeout = 2h
Wait for <duration>
before declaring a state-changing action a failure.
A per-action <action>_timeout
can override this value.
type
required: false
scopable: false
The resource driver name.
unprovision_timeout
required: false
scopable: true
convert: duration
Example:
unprovision_timeout = 1m30s
Wait for <duration>
before declaring the action a failure.
Takes precedence over timeout
.