-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EchoCallset] Retry with more memory VCF extract [VS-1351] #8814
[EchoCallset] Retry with more memory VCF extract [VS-1351] #8814
Conversation
910d7d3
to
88ebd90
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
link to test run?
exit 1 | ||
fi | ||
|
||
gatk --java-options "-Xmx${memory_mb}m" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oooooh i didn't know we could do this!
(can we do this all over the VAT pipeline too!??!?!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure why not. The hard part is remembering to tick the 'Retry with more memory' option when launching the workflow lol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And we already need to remember to click on the reference disk checkbox for that...
Intentionally failing test run here where I sabotaged the code to simulate an out of memory condition. You can see on the first attempt memory usage looks like
after three retry-with-more-memory retries, things look like:
|
No description provided.