When uploading a backup, I am constantly hitting 429s, which results in the entire upload failing, resulting in me being forced to upload via CLI. This is because the frontend is not properly handling 429 responses. My personal suggestion is to either remove ratelimiting on that endpoint or just have the client properly handle it.
AI-generated summary
The discussion addresses an issue where backup uploads frequently fail due to 429 (Too Many Requests) errors, causing uploads to abort. darkpixlz notes that the frontend does not properly handle 429 responses, suggesting either removing rate limiting or improving client-side handling. sam agrees, proposing to relax rate limiting and use larger upload chunks. gerhard suspects the issue may stem from Uppy’s default chunk size (5 MB) and confirms that the uploader likely doesn’t handle 429 errors, stating they will investigate and consider relaxing the rate limit.
2 Likes
oh, those parts look really really small.
Maybe the fix is twofold, relax rate limiting and use larger chunks.
Will alert the team in case they have ideas.
1 Like
Must be an issue with the Uppy chunk size. It’s strange that nobody else encountered this before. I thought our default chunk size was 5 MB. I’ll investigate. I’m pretty sure our Uppy uploader doesn’t handle 429 codes, but I’ll check if we can relax the rate limit a bit. But I think it’s just the default rate limit kicking in.
2 Likes