search

dotCMS / core

Headless/Hybrid Content Management System for Enterprises
http://dotcms.com
Other
845 stars 465 forks source link

Chunk larger file uploads to avoid timeouts #26647

Open swicken-dotcms opened 10 months ago

swicken-dotcms commented 10 months ago

Parent Issue

No response

User Story

As a user, I want to be able to upload large files to dotCMS without worrying about the load balancer or proxy timing out the connection.

Acceptance Criteria

  1. Chunk larger uploads for all file asset types on the front end
  2. Update the backend to accept chunks file uploads (put them in temporary storage and assemble them after completion)

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

Related ticket: https://dotcms.zendesk.com/agent/tickets/114000

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

damen-dotcms commented 10 months ago

Scott gave an example where the client needed to upload a file that was 1.25 gigabytes.

So yeah that's huge! But real clients are hitting limitations with the current setup.

We should aim for 2 gigabytes just to have some padding.

sfreudenthaler commented 10 months ago

Scott gave an example where the client needed to upload a file that was 1.25 gigabytes.

So yeah that's huge! But real clients are hitting limitations with the current setup.

We should aim for 2 gigabytes just to have some padding.

Should max file size and chunk size be configurable per instance? Maybe with a envvar or even a config option where the change would take effect without the need for service restarts?