Ever wish you could automatically remove your unwanted output files from a submission without having to manually review them? If so, take this two minute survey and tell us more.
Latest Release: 1/10/19
Release Notes can be found here.

workflows submitted later start running while workflows submitted earlier still waiting?

esalinasesalinas BroadMember, Broadie ✭✭✭
edited February 2017 in Ask the FireCloud Team

I have two submissions launched about 6 minutes apart:

A more recent one:

February 24, 2017, 9:45 AM
Submitted
esalinas/benchmark_prep_one_m_scatter_wxs_n1_standard_32
10_RAND_BRCA_WGS (pair_set)
[email protected]
92d2e106-252b-43ae-99fc-4f935f5dc487

The one submitted first:

February 24, 2017, 9:39 AM
Submitted
esalinas/benchmark_prep_one_m_scatter_wxs_n1_highmem_32
10_RAND_BRCA_WGS (pair_set)
[email protected]
eed1045d-b768-41ae-8658-de3d75440b09

I note that in the one submitted first (eed....) that all the workflows are in "Launching" state but that in the workflow submitted second (92d...) that half are in "Running" state. This way, it seems that the second submission somehow "jumped the line" or "jumped the queue". Is this the right behavior? What is the right behavior? What is the expected behavior?

Both of these submissions are in the same workspace and run on the same pair-set from the data-entity model.

Issue · Github
by Geraldine_VdAuwera

Issue Number
1764
State
open
Last Updated

Best Answer

Answers

Sign In or Register to comment.