Question

Spaces and copyObject issues/timeouts

Currently trying to the copyObject call from the S3 SDK and it is timing out. We have been noticing this issue occasionally over the last few weeks. Are there currently any known issues with spaces when trying to copy objects from one place to another within the same Spaces domain?

Subscribe
Share

Same here with SFO2. Copying from one space to another under the same account. On Amazon s3 this is almost instant regardless of size as I’ve tested it with files > 500MB.

Half the time they take 30 seconds just to get a response to copyObject and the other half the time they timeout.

This is a critical issue for us.

This is happening to spaces in NYC3

Also trying to rename items with in the Space appears to be really slow and doesnt work all the time.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

After extensive testing it appears to be a design flaw in the DigitalOcean Spaces implementation itself and I’m quite surprised (and concerned) that DO engineering hasn’t responded to this. Both copy and rename take an unusual amount of time. You can even see this renaming an object in the DO dashboard/ui. A rename shouldn’t take 15-20 seconds. I’m not sure how Amazon handles this in their S3 implementation but it’s almost instant.

I would highly advise anyone considering switching from AWS to DO Spaces to be 100% sure you’ve tested the endpoints you need and to make no assumptions. The API is the same but the infrastructure and underlying design is most certainly not.

Hello, @austinbischoff

There was an Issue with Spaces Availability in FRA1 a few days ago - https://status.digitalocean.com/incidents/51vcqfrqhb8s which was successfully resolved by our engineers.

At the moment everything should be working fine including in NYC3 as well. If you’re still experiencing issues please submit a support ticket with detailed information about the issue and our support team will be more than happy to assist you.

Regards, Alex