Skip to content
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

storage/swift: upload fails on large objects #257

Closed
buchanae opened this issue Oct 10, 2017 · 3 comments · Fixed by #356
Closed

storage/swift: upload fails on large objects #257

buchanae opened this issue Oct 10, 2017 · 3 comments · Fixed by #356

Comments

@buchanae
Copy link
Contributor

Getting upload errors "Too Large Object" from swift.

Related info:
https://godoc.org/github.com/ncw/swift#Connection.DynamicLargeObjectCreate

rclone/rclone@cc7b9af

@buchanae buchanae changed the title swift: upload fails on large objects storage/swift: upload fails on large objects Nov 4, 2017
@adamstruck
Copy link
Contributor

adamstruck commented Nov 22, 2017

I was able to upload a 5 GB file without a problem using:

{
  "name": "Large file download/upload example",
  "executors": [
    {
      "image": "biocontainers/samtools:1.3.1",
      "command": ["sh", "-c", "samtools view /tmp/inputs/NA21097.cram | head -n 100 | md5sum"],
      "stdout": "/tmp/outputs/stdout"
    }
  ],
  "inputs": [
    {
      "url": "swift://funnel-test/inputs/NA21097.mapped.ILLUMINA.bwa.GIH.low_coverage.20120522.bam.cram",
      "path": "/tmp/inputs/NA21097.cram"
    }
  ],
  "outputs": [
    {
      "url": "swift://funnel-test/outputs/NA21097.cram",
      "path": "/tmp/inputs/NA21097.cram"
    },
    {
      "url": "swift://funnel-test/outputs/NA21097_100.md5sum",
      "path": "/tmp/outputs/stdout"
    }
  ]
}

UPDATE:

This test passed only because this object was just under the limit. According to the Openstack docs, an individual object cannot be larger than 5 GB.

https://docs.openstack.org/swift/latest/api/large_objects.html

@buchanae
Copy link
Contributor Author

did you try it with #356 yet?

@adamstruck
Copy link
Contributor

Yeah I tested it and have everything working in #356.

@buchanae buchanae added this to the 0.5.0 milestone Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants