Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add suggestion on increasing upload part size #626

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add suggestion on increasing upload part size #626

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,9 +234,14 @@ This means that there is not control on how fast a single segment would be uploa

The plugin rate-limit is complementary to Tiered Storage Quotas.

#### S3 Multipart Upload
#### S3 Multi-part Uploads

When uploading processed segments and indexes, multipart upload is used to put files on S3 back-end.
When uploading processed segments and indexes, multipart upload is used to put files on the storage back-end (e.g. AWS S3).

> [!IMPORTANT]
> To control the amount of upload part requests that are executed per segment, each storage back-end has a size configuration.
> Consider increasing this value (e.g. 10x) to reduce the number of requests, and therefore its costs
> (default: minimum part size, e.g. `rsm.config.storage.s3.multipart.upload.part.size` for S3 is 5 MiB)
Even though, multipart transactions are aborted when an exception happens while processing,
there's a chance that initiated transactions are not completed or aborted (e.g. broker process is killed) and incomplete part uploads hang without completing a transaction.
Expand Down
Loading