orcaLog in

Pipelines

mojo_history

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 ↗
0 running of 1, 245 queued

Start runs docs

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

Queues a single run over every key 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_history <range>
/opt/orca/pipelines/mojo_history 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.