-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Long processing times while uploading to S3 #19223
Copy link
Copy link
Open
Labels
0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap25-feedbackbugfeature: object storagehotspot: file transfer performanceupload & download performance related optimizationsupload & download performance related optimizations
Metadata
Metadata
Assignees
Labels
0. Needs triagePending check for reproducibility or if it fits our roadmapPending check for reproducibility or if it fits our roadmap25-feedbackbugfeature: object storagehotspot: file transfer performanceupload & download performance related optimizationsupload & download performance related optimizations
Type
Fields
Give feedbackNo fields configured for issues without a type.
Running Nextcloud 17.0.3 behind Cloudflare works fine, unless the upload processing time takes longer than 100s (in our case, uploading files bigger than 2GB trough WebUI to a S3 primary backend). In that case, Cloudflare returns a
524.Error when assembling chunks, status code 524Contacting Cloudflare about this hits on a:
Cloudflare will typically wait for a HTTP response from origin server for 100 seconds. If no response (or
<8Kb) is sent by the origin in that time, Cloudflare will close the connection and serve a 524 error page.So the question is, can (should?) Nextcloud detect those long running processing times and send a
keepaliverequest every (say) 60 seconds to avoid these problems on some proxies like Cloudflare?