Page MenuHomePhabricator

[keyserver] Introduce concept of auxiliary node for running certain cronjobs
ClosedPublic

Authored by ashoat on Aug 21 2024, 6:00 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 13, 9:01 PM
Unknown Object (File)
Tue, Nov 12, 6:04 PM
Unknown Object (File)
Fri, Nov 8, 7:03 PM
Unknown Object (File)
Fri, Nov 8, 7:03 PM
Unknown Object (File)
Fri, Nov 8, 7:01 PM
Unknown Object (File)
Fri, Nov 8, 1:33 AM
Unknown Object (File)
Sun, Nov 3, 5:33 AM
Unknown Object (File)
Sep 25 2024, 1:30 AM
Subscribers

Details

Summary

We'll use the auxiliary node for running the the Comm team dev scripts (RUN_COMM_TEAM_DEV_SCRIPTS) and for database backup.

Depends on D13134

Test Plan

Ran this on my personal server and confirmed that it worked

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Unfortunately Phabricator got a little confused on this diff, and is marking some changes in a confusing way. Basically I just pulled out three cronjobs here and put them at the end:

  1. backupDB
  2. createDailyUpdatesThread
  3. postLeaderboard

The first is additionally gated by COMM_JSONCONFIG_facts_backups, and the other two are additionally gated on RUN_COMM_TEAM_DEV_SCRIPTS. When their gates are enabled, they can be run on either the primary or auxiliary nodes.

This revision is now accepted and ready to land.Aug 21 2024, 10:48 PM