Arvados

Well, just pulling out to the Workbench homepage "there are N jobs ahead" would be a great start, I didn't think to look inside the pipeline. Or job.

My specific issue is I'm trying to learn Arvados by running short pipelines, and I just want to know if I should expect my pipeline to take longer than a minute to start running, in which case I'll go do something else. After hitting run I'll go to the homepage and stare expectantly at the pipeline (the page does a good job of conveying that it is actively tracking the job and I don't need to hit refresh)

So my question is actually "Why is my pipeline not running" and I try to estimate it by "How long did the previous ones take to start" and I can't because it seems random to me.

Other possible solutions: A help topic, "Why isn't my job running" that explains the possible reasons.

At the core, being able to play around and get results quickly will make it more pleasant to learn Arvados. Sandboxes? Arv run? Arvados-like local docker? Immediately running pipelines? are all addressing this.

• All worker nodes are busy. Nodemanager will probably do something about this in 10(?) seconds.
• Some worker nodes are bootstrapping or idle, but they'll be consumed by jobs ahead of yours. Nodemanager will probably do something about this in 10(?) seconds.
• After accounting for jobs ahead of yours in the queue, #nodes needed by your job are bootstrapping. Of the workers needed, the most recently started is X seconds old; bootstrapping is usually done in Y seconds according to workbench config (or according to API? a configured or computed ETA could be offered in the nodes#index API response).
• There are enough idle nodes to run your job now. Your job will probably start in 10(?) seconds.

• Pipeline instance #show → Components
  • If component state is Queued, show ETA / summary of system state as it relates to this job ("worker nodes spinning up, ETA 2m")
• Dashboard → Active pipelines
  • (?)Show nearest ETA of any queued job (if any)
• Dashboard → Compute and job status
  • (?) Show table of nodes (name, state, cores, ram, scratch)
  • Replace "submitted" column with ETA

• If there are enough idle nodes to run all jobs in the queue up to & including this one, ETA is 10(?) seconds.
• Hard to say much otherwise. Number of jobs ahead of yours?
• (How does Workbench know nodemanager isn't running?)