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
Invalid server response makes Google pipelines execution to crash #1163
Comments
FYI, the extension of nextflow.logs.gz is misnamed as it is a compressed tarfile. Please run tar xzf to open it. Sorry for the confusion. |
…#1163 Signed-off-by: Ivkovic <sinisa.ivkovic@gmail.com>
…w-io#1163 Signed-off-by: Ivkovic <sinisa.ivkovic@gmail.com>
I've not run into this error for a while, however I believe I just encountered it again in 19.07.0-edge:
|
The tar looks corrupted. May you upload it again (maybe using zip)? |
That one is not a tar file, just the log file gzipped. Sorry for the previous confusion. I've attached it here again zipped. I suspect the core issue starts from this line: Jul-18 13:31:20.487 [Task submitter] ERROR nextflow.processor.TaskProcessor - Error executing process > 'salmon_quant (TCGA-OR-A5JI-01A)' |
The error stack trace in the log attached seems related to a different error. Please open a separate issue for it. Closing this. |
Bug report
Expected behavior and actual behavior
Errors returned from the Google Genomics Pipelines API appear to generate exceptions which bubble up and cause the workflow to shutdown.
Using retries or an error strategy of ignore does not solve the problem.
Steps to reproduce the problem
The problem is sporadic. I have run this pipeline against 100 samples without error. However, when run against ~1000 samples, the error usually appears.
Program output
The nextflow log file from 2 distinct failures is attached. One fails in
GooglePipelinesTaskHandler.checkIfCompleted() with 503 Service Unavailable
and the other in
GooglePipelinesTaskHandler.submit() with 410 Gone
For the "503 Service Unavailable" response, the recommendation is to retry with a backoff.
"The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff."
See: https://cloud.google.com/genomics/reference/rest/Shared.Types/Code
For the second case, it is not clear whether the "410 Gone" is truly accurate or if this might be also a transient condition.
Environment
Additional context
nextflow.logs.gz
rna_seq_quant.nf.gz
The text was updated successfully, but these errors were encountered: