Skip to content

Conversation

@juliusknorr
Copy link
Member

@juliusknorr juliusknorr commented Oct 11, 2022

Otherwise we try to allocate ~500MB in memory which does fail on larger file uploads with our default memory limit. We only need the put file limit configured anyways.

Steps to reproduce on 24+:

  1. use s3 primary storage
  2. upload a 500mb file through the web ui or clients

Before that change the MOVE request ended in an Allowed Memory Size Exhausted error.

@juliusknorr
Copy link
Member Author

@juliusknorr juliusknorr requested review from a team, icewind1991 and skjnldsv and removed request for a team October 11, 2022 13:39
@juliusknorr
Copy link
Member Author

/backport to stable25

@juliusknorr
Copy link
Member Author

/backport to stable24

Copy link
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sense! 👍

@juliusknorr juliusknorr changed the title Avoid allocating too much memory for the buffer Avoid allocating too much memory for the buffer on s3 uploads Oct 11, 2022
Copy link
Member

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@skjnldsv skjnldsv added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Oct 12, 2022
@skjnldsv skjnldsv merged commit d936694 into master Oct 12, 2022
@skjnldsv skjnldsv deleted the bugfix/noid/s3-upload-memory branch October 12, 2022 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish bug feature: object storage regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants