Why is R2 Sippy Migration not downloading files above 1GB at a shot

Developers
1

For Workes & Pages, what is the name of the domain?

N/A

What is the issue or error you’re encountering

R2 Sippy Migration not downloading files above 1GB?

What steps have you taken to resolve the issue?

I implemented Sippy Migration for my r2 bucket. But I notice If I call a file which isn’t current in R2 bucket it makes request to source bucket, gets the file and copy it to R2 bucket at one shot.

This only happens for files between 1MB and 1GB. but for files above 1GB. It doesn’t download it at a shot. how do I solve this??

2

I don’t know if there’s a 1GB hard limit, but the multi-part download is stated in the caveats part of the Sippy documentation:

Sippy makes autonomous decisions about the operations it uses when migrating objects to optimize for performance and network usage. It may choose to migrate an object in multiple parts… ETag calculation.

You may submit feedback on this using the Sippy (beta) feedback form or in the #r2-storage channel or on the Cloudflare Developer Discord.

3

Yes I did see that. But I think larger file for Sippy is around 5GB or I stand to be corrected.

I have done several get requests on that same file It wouldn’t still complete and wouldn’t load the file either.

4

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.