Unconfigured MinIO part size causes memory bloat during backups

warning

Resource ContentionUpdated Jan 28, 2025(via Exa)

Sources

fix(backup): memory control consumption by setting minio specific part size · Pull Request #7057 · weaviate/weaviategithub.com

Technologies:

Weaviatesubject

MinIOThe root cause of this issue originates in MinIO

How to detect:

When backup operations are triggered without MinIO part size configured in the minio-go client, it defaults to the maximum part size (5TiB), causing excessive memory buffer allocation. This results in observable memory growth during backup operations.

Recommended action:

Update Weaviate to version that includes PR #7057 (merged into stable/v1.25), which sets the MinIO multi-part upload part size to 16MB (the minimum for minio-go). Monitor memory metrics (heap allocated, heap in use, process resident memory) before and after backups to verify reduced memory consumption.