# 迁移至 S3 的任务因请求过多而失败

**URL:** <https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305>\
**Category:** Self-hosting\
**Tags:** s3\
**Created:** [2019 年1 月 11 日 18:20 UTC](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305 "2019-01-11T18:20:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

作者： ![marcozambi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcozambi/32/119505_2.png) [@marcozambi](https://meta.discourse.org/u/marcozambi)\
发布日期： [2019 年1 月 14 日 16:39 UTC](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305/4 "2019-01-14T16:39:13Z")

</div>

> [@zogstrip](#):
>
> Do you have lots of small files?

Yes. About 37000 “originals” and of course 3 times more in the “optimized” directory. In total about 120000.

> [@zogstrip](#):
>
> Also, the `s3cmd sync` will “break” any attachments (they will lose their file name).

This I do not understand, what do you mean? The uploads I copied manually to Spaces were identical in name and path placement on Spaces with those on my local disk. I made several tests before the final rebake, that just ended and was fully successful.

> [@zogstrip](#):
>
> In theory, it should be. But it’s not convenient to set the arguments in one place (settings UI) and use them in another (rake task).

I see your point, but then please consider that setting environment variables might have some unwanted consequences and, at least in my experience, required to rebuild the container and broke the UI as I [explained here](https://meta.discourse.org/t/migration-of-system-stored-images-to-s3-after-configuration-change/19605/52).

---

_[View the full topic](https://meta.discourse.org/t/migrate-to-s3-task-fails-for-placing-too-many-requests/106305)._