orcaLog in

Pipelines

mojo_activity

Progress

Runs at onceRuns of this pipeline going now, out of the most the scheduler starts at once (max_runs); the others wait in the queue. Fill runs come on top, up to fill_max_runs. Docs ↗
1 running of 1, 592 queued
FollowingA sensor runs the partitions of the tables it reads as they get snapshots. This is how many of those partitions it has done, and the ones it hasn't: going, failed, or not queued yet (a backfill queues them). They are behind on Coverage. Docs ↗
gharchive and mojo_repos (gharchive.releases, gharchive.repo_hour and mojo.repos): 45 of 1008 days done; 963 behind: 593 running or queued and 370 not queued yet
CoverageWhich days or months a run has done, failed or not reached yet, as a calendar on the Operate tab. Docs ↗
The calendar

Coverage

MonthYear
April 2023
  • 1, 2023-04-01 behind what it follows
  • 2, 2023-04-02 behind what it follows
  • 3, 2023-04-03 behind what it follows
  • 4, 2023-04-04 behind what it follows
  • 5, 2023-04-05 behind what it follows
  • 6, 2023-04-06 behind what it follows
  • 7, 2023-04-07 behind what it follows
  • 8, 2023-04-08 behind what it follows
  • 9, 2023-04-09 behind what it follows
  • 10, 2023-04-10 behind what it follows
  • 11, 2023-04-11 behind what it follows
  • 12, 2023-04-12 behind what it follows
  • 13, 2023-04-13 behind what it follows
  • 14, 2023-04-14 behind what it follows
  • 15, 2023-04-15 behind what it follows
  • 16, 2023-04-16 behind what it follows
  • 17, 2023-04-17 behind what it follows
  • 18, 2023-04-18 behind what it follows
  • 19, 2023-04-19 behind what it follows
  • 20, 2023-04-20 behind what it follows
  • 21, 2023-04-21 behind what it follows
  • 22, 2023-04-22 behind what it follows
  • 23, 2023-04-23 behind what it follows
  • 24, 2023-04-24 behind what it follows
  • 25, 2023-04-25 behind what it follows
  • 26, 2023-04-26 behind what it follows
  • 27, 2023-04-27 behind what it follows
  • 28, 2023-04-28 behind what it follows
  • 29, 2023-04-29 behind what it follows
  • 30, 2023-04-30 behind what it follows

0 done · 0 failed · 0 running or queued · 30 behind what it follows · 0 not run · 0 outside the pipeline's range

Behind: gharchive.releases, gharchive.repo_hour and mojo.repos has it, but no run of this pipeline has done it, failed on it or is going; a backfill queues it.

Start runs docs

Queues a run for each day in the range that hasn't succeeded and isn't in a queued or running run.

Queues a single run over every day in the range, done or not; refused while a queued or running run has one of them.

Same from the command line (on the control instance today, remotely once #111 lands):

orca backfill mojo_activity <range>
/opt/orca/pipelines/mojo_activity run --partitions <range>

The second runs in that shell's process rather than queuing it; orca has no command that queues one run. The scheduler (orca scheduler) starts queued runs, up to 1 at once.

Stop runs

Cancelling stops runs that are queued or waiting to be retried, and asks running ones to stop before their next step. Pausing stops the scheduler starting its runs, which stay queued; runs already going go on.