Closed Bug 1591994 Opened 5 years ago Closed 5 years ago

bump GCP pools more to get smaller end-to-end times

Categories

(Release Engineering :: General, enhancement)

Product:
Release Engineering
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

(Whiteboard: [releaseduty])

Attachments

(2 files)

[k8s] greedily bump beetmover and signing max_replicas
55 bytes, text/x-github-pull-request
Details | Review
[k8s] greedily bump balrog max_replicas
55 bytes, text/x-github-pull-request
Details | Review

We're still seeing at times, ~350-400 signing jobs pending and sometimes up to 50 beetmover jobs pending. We should upgrade the limit from 40 to more.

Beetmover has no restrictions but for signing, I'll ask in autograph first to ensure we're not flooding the API.

Assignee: nobody → mtabara

Up to 80 beetmoverworkers and 100 signingworkers from now on.

I've deployed the k8s configs and pushed the new Docker images in beetmoverscript and signingscript.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
See Also: → 1591373
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: