Provide mechanism to tune the sysctl param fs.aio-max-nr on the host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
New
|
Undecided
|
David Vallee Delisle |
Bug Description
Previously (for example, in RHOSP 13) libvirt-daemon RPM was installed on compute nodes and it provided /usr/lib/
Documentation tells us that this number should be calculated as number of virtual disks on the host * 128. As a result default limit leaves us with 512 virtual disks, but KCS providing deployment limitations https:/
I am not sure how default value would behave in containerized environment, but this looks like a possible problem that requires second look.
[1]
[root@compute-1 ~]# cat /usr/lib/
# The kernel allocates aio memory on demand, and this number limits the
# number of parallel aio requests; the only drawback of a larger limit is
# that a malicious guest could issue parallel requests to cause the kernel
# to set aside memory. Set this number at least as large as
# 128 * (number of virtual disks on the host)
# Libvirt uses a default of 1M requests to allow 8k disks, with at most
# 64M of kernel memory if all disks hit an aio request at the same time.
fs.aio-max-nr = 1048576
Changed in tripleo: | |
assignee: | nobody → David Vallee Delisle (valleedelisle) |
Fix proposed to branch: stable/train /review. opendev. org/c/openstack /tripleo- heat-templates/ +/827018
Review: https:/