-
Notifications
You must be signed in to change notification settings - Fork 7
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
non-deterministic sql panic #34
Comments
dxWDL uses the latest dxda on master branch. This looks like a new variation of an old problem. We'll need to investigate. Does this happen towards the end of the download phase? |
Thanks @orodeh -- you can see the context from the job I linked above. It's always after downloads complete. Pasted here:
|
Oh, I think I know what the problem is. The thread that periodically reports on download progress has not been shut down, and it continues to query the database after it has already been closed. |
Should be an easy fix. |
Fixed on master. |
Please check it out, new code is part of the new dxWDL release https://github.com/dnanexus/dxWDL/releases/tag/v1.47 |
Hm... I still get this in dxWDL 1.47: Analysis: https://platform.dnanexus.com/projects/F8PQ6380xf5bK0Qk0YPjB17P/monitor/analysis/Fpyz1B80xf5qY28X2X8YY3z4
|
This is strange, because the continuous reporting thread has been shut down at this point. I am not sure how it is still operating. This will have to be reopened. |
Hi @dpark01 we believe we found the issue and are testing an implementation fix. We will let you know when a dxWDL release will contain this fix. Thanks for reporting. |
Hi @dpark01, we have released dxWDL with the fix. Please let us know if the issue persists or if you encounter any other issues. Thanks! |
v1.48.1 release fixed both database closed (this issue) and 502 error. |
Hi folks,
I've noticed that with some low frequency at random, I get jobs failing with the following immediately after localizing files with dxda:
These often succeed upon relaunch. Here is one example job that came from this larger analysis.
Do you know what causes that behavior?
If it matters, these workflows are all generated via dxWDL 1.46.4. Since this often succeeds after relaunch, would it make sense for dxWDLrt to capture exit code 2 from dxda and just retry up to some reasonable retry limit?
The text was updated successfully, but these errors were encountered: