From 8f916dc736945a0f82e381974cb14cd74447f08b Mon Sep 17 00:00:00 2001 From: Jeremy Stanley Date: Thu, 16 Mar 2023 19:26:58 +0000 Subject: [PATCH] Restore rax-ord quota but lower max-concurrency Looking at our graphs, we're still spiking up into the 30-60 concurrent building range at times, which seems to result in some launches exceeding the already lengthy timeout and wasting quota, but when things do manage to boot we effectively utilize most of max-servers nicely. The variability is because max-concurrency is the maximum number of in-flight node requests the launcher will accept for a provider, but the number of nodes in a request can be quite large sometimes. Raise max-servers back to its earlier value reflecting our available quota in this provider, but halve the max-concurrency so we don't try to boot so many at a time. Change-Id: I683cdf92edeacd7ccf7b550c5bf906e75dfc90e8 --- nodepool/nl01.opendev.org.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nodepool/nl01.opendev.org.yaml b/nodepool/nl01.opendev.org.yaml index 03f6de72ce..d6f484af13 100644 --- a/nodepool/nl01.opendev.org.yaml +++ b/nodepool/nl01.opendev.org.yaml @@ -194,14 +194,14 @@ providers: # timeout but mitigate node request delays by not retrying failures. Also # try to substantially reduce the number of instances we launch in # parallel. - max-concurrency: 10 + max-concurrency: 5 launch-retries: 1 launch-timeout: 900 rate: 0.01 diskimages: *provider_diskimages pools: - name: main - max-servers: 100 + max-servers: 195 labels: labels: *provider_pools_labels