AWS s3 upload not complete #3271
Unanswered
hurrialice
asked this question in
Q&A
Replies: 1 comment
-
I think my major confusion is that I don't see any error message on log files and the problem was only picked up when I tried to load those BAMs to IGV. I wonder if there is anything I can do to make sure the upload is robust -- e.g. compare hashes of my local files vs s3 uploaded files? Thanks for any insights in advance. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi nextflow team, thanks for the great work!
I have been running nextflow on HPC and upload results to a s3 bucket:
while
params.outdir
is a s3 bucket with write access provided by default aws profile.My aws scope in nextflow.config looks like this:
However when I have multiple large files (e.g. BAMs) to upload concurrently, I often get incomplete files in s3. In a recent test with 11 concurrent BAM (each is about 50G) uploads, I got 5 partial BAM files -- notably, each partial BAM file is either 500MB or 550MB. I wonder if you have any suggestion on tweaking my config above. I was suspecting the upload was bottlenecked by uploadMaxThreads*uploadChunkSize but I wasn't sure... I did not find anything useful from
.nextflow.log
Thanks for your time! Any suggestion is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions