admin管理员组

文章数量:1302360

I have deployed ownCloud Infinite Scale (OCIS) (which has an s3 storage as a backend to store user files )in a Kubernetes cluster using Helm. The service is up and running, and I can successfully upload files using web UI. I am doing some testing on file uploading using rclone with WebDAV requests. I can successfully upload small files using rclone with WebDAV but large file uploads (threshold value 8MB+) fail with the following error:

wsarecv: An existing connection was forcibly closed by the remote host.

What I Tried:

  1. Increased timeouts in Ingress
  2. proxy-body-size 25g
  3. rclone command modified like this -> rclone copy "C:\Users\Downloads\rclonetest\10MB.txt" ocis-dev:spaces/{space_id}
    --no-check-certificate -P -vv --timeout=7200s --contimeout=3600s --transfers=1 --disable-http2

Questions:

  1. Are there default upload size limits in OCIS WebDAV? If so, how can I check and modify them in a Kubernetes deployment?
  2. Do I need to explicitly set any env variables in the helm chart? If so, what values are recommended for large file uploads (e.g., 5GB+)?
  3. Could this be a reverse proxy (NGINX) buffering issue despite proxy-body-size 25g being set?
  4. Is there a way to enable chunked uploads in WebDAV with OCIS?

Any insights or solutions would be greatly appreciated!

Update: rclone copy "C:\Users\rclonetest\test.txt" ocis-dev:spaces/{space_id} --no-check-certificate -P -vv --timeout=7200s --contimeout=3600s --transfers=45 --disable-http2 --retries=10 --low-level-retries=15

When I used this rclone command, I was able to upload a 27.3 MB file into the OCIS.

Thank You

本文标签: