1633424 - Spread daily crontasks over time

Status: RESOLVED DUPLICATE of bug 1633440

(Taskcluster :: Services, enhancement)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

bpitts39260:templates bpitts$ rg -l 'schedule: 0 0 * * *'
taskcluster-queue-cron-expireTaskDependency.yaml
taskcluster-web-server-cron-cleanup-expire-access-tokens.yaml
taskcluster-github-cron-sync.yaml
taskcluster-auth-cron-purgeExpiredClients.yaml
taskcluster-worker-manager-cron-expire-workers.yaml
taskcluster-queue-cron-expireWorkerInfo.yaml
taskcluster-queue-cron-expireTaskGroupSizes.yaml
taskcluster-queue-cron-expireArtifacts.yaml
taskcluster-purge-cache-cron-expireCachePurges.yaml
taskcluster-queue-cron-expireQueues.yaml
taskcluster-queue-cron-expireTaskGroups.yaml
taskcluster-web-server-cron-cleanup-expire-auth-codes.yaml
taskcluster-web-server-cron-scanner.yaml
taskcluster-queue-cron-expireTaskGroupMembers.yaml
taskcluster-queue-cron-expireTask.yaml
taskcluster-index-cron-expire.yaml
taskcluster-queue-cron-expireTaskRequirement.yaml

These are causing a spike in CPU usage on the DB server.

Comment 2

[[:samihda]]

This is just a matter of changing the cron job strings, right?
I mean of course, we need to decide on the new schedule first.