Categories

Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
2. Be as detailed as you can when describing your problem, i.e. tell us what happened or didn't happen rather than "it didn't work" or "it failed".
3. Include the full text of any error messages you encounter.
4. Include relevant code snippets in the body of your post (see formatting tips below) and attach your full WDL script using the "Attach a file" link below the comment box.
5. Tell us what version of Cromwell, wdltool or any other software involved you are using.
6. Tell us what platform you are running on.

Get notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

Formatting tip!

Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block as demonstrated here.

Jump to another community

To celebrate the release of GATK 4.0, we are giving away free credits for running the GATK4 Best Practices pipelines in FireCloud, our secure online analysis portal. It’s first come first serve, so sign up now to claim your free credits worth $250. Sponsored by Google Cloud. Learn more at https://software.broadinstitute.org/firecloud/documentation/freecredits

Question on caching

Say I have 1 workflow that has 1000 scatter chunks, with caching pointing to a mysql database. The workflow failed when 100 scatter tasks were complete, but a further 400 was still running at the time of failure (an LSF system) and were able to successfully complete. Will the 400 tasks that finish after the main cromwell process failed still be recorded in the cache?

Best Answer

This relates to a separate question I posted where the cromwell process itself dies because of a race condition related to the stderr file. On my setup (a LSF system), this means the cromwell process dies while the tasks keep on running to completion, but your answer seem to imply that since the cromwell process itself died, even though the "orphaned" tasks finished completely, since the main cromwell process, which is responsible for writing to cache, is not alive, the completed tasks will not be registered in the cache. Am I correct?

Does that just keeps the main cromwell process alive? What if cromwell fails regardless? AKA is the main cromwell process the only one that is writing to cache so to speak? Or is the child process also writing to cache?

This relates to a separate question I posted where the cromwell process itself dies because of a race condition related to the stderr file. On my setup (a LSF system), this means the cromwell process dies while the tasks keep on running to completion, but your answer seem to imply that since the cromwell process itself died, even though the "orphaned" tasks finished completely, since the main cromwell process, which is responsible for writing to cache, is not alive, the completed tasks will not be registered in the cache. Am I correct?