Increase disk_allocation_ratio to 4
With a max of 60 envs, we're starting to hit scheduling errors due to lack of disk space on some of the compute nodes. In reality, none of the compute nodes are using more than 61% of their disk and most are under 50%, so a 33% increase in overcommit should be safe enough. We may also want to increase the scheduler retries to help with this problem. Part of the issue is that most of the compute nodes have sufficient disk available, but if we happen to get unlucky and pick three in a row that don't then the instance fails. More scheduler retries would help with that. Change-Id: Ifb2db1ddafd183aa4c9584b406e3b47bf7b0c5a9
This commit is contained in:
parent
17f4c8673d
commit
26e940c68f
|
@ -13,7 +13,7 @@ parameter_defaults:
|
|||
neutron::network_device_mtu: 1500
|
||||
# rh2 disks are small, we're relying on the fact that CI jobs at different stages wont
|
||||
# ever use peak disk usage together (also they don't use all thats allocate in the flavor)
|
||||
nova::scheduler::filter::disk_allocation_ratio: 3
|
||||
nova::scheduler::filter::disk_allocation_ratio: 4
|
||||
# More than 4 Heat engine workers allows Heat to essentially DoS the other services
|
||||
# if a lot of jobs come in at once. This is borrowed from
|
||||
# worker-config-mitaka-and-below.yaml. Once rh1 is on a newer release we should
|
||||
|
|
Loading…
Reference in New Issue