[Feature] Remove MinIO (memory consumption)

[codeurimpulsif]

Is your feature request related to a problem? Please describe

MinIO is OOM killed every 2 or 3 days, cleaning storage now take a lot of time while before it takes only 10 minutes.

Describe the solution you'd like

I think we can try to remove MinIO and just use Django to access files from other servers. This also remove a dependency to S3 storage.

Describe alternatives you've considered

• Using another S3 storage software like Garage

Additional context

Since last versions MinIO use a lot more memory and is OOM killed every 2 or 3 days.

MinIO seems to focus on big Kubernetes stuff and not small infrastructures anymore, closing all issues about this memory consumption with a "MinIO preallocates buffers for incoming data now" message.

[codeurimpulsif]

Since 2 days, MinIO is in maintenance mode (aka "not Free anymore and will die soon").

We need to switch to Garage or on disk as soon as possible, but I'm not a really good dev on this part…

[douardda]

It's unclear to me whether this issue is code related ("but I'm not a really good dev on this part..") or purely a deployment/ops one.

Are the deployment/ops aspects of hosting exodus described somewhere?

Let me also suggest seaweefs as possible tool for s3-like storage.

[codeurimpulsif]

@douardda thanks for your comment.

It's a pure dev issue, the deployment/ops part is easy for me (I'm the system administrator of Exodus Privacy).

To be clear, we need to :

• Change the code on exodus side which handle MinIO to be sure it's compatible with Garage (or make it compatible with any S3-like software, which would be cooler)
• Test it and create a new exodus release with this functionnality (a 2.0 version I think, because it's a breaking change)
• Plan a maintenance window to migrate data from MinIO to Garage or other S3-like and deploy the new exodus version (this part is only for me and will be easy for me)

SeaweeFS seems cool too. I think I like Garage because it's a cool project from a friendly organization, so I'm more confident with this kind of projects ahah ^^

[douardda]

Ah indeed usage of the minio module (and django-minio-storage) is actually everywhere in the code base... 😱

For Garage, sure, I'm just a bit puzzled by the lack of activity on the repo...

Not checked what Garage does in the background, but one key feature of seaweed is the ability to store small objects efficiently (packing them in volume files to prevent space amplification due to minimal/fixed block size of the backend storage). So it depends a lot on the type of storage pattern you have to deal with.

[almet]

Hi, I've had a quick look, and wonder if it would be possible to actually continue using the minio client, while shifting the storage backend to something else (yay for garage!). My understanding is that minio uses the S3 protocol, unless you're using some minio specifics?

On their documentation, garage points to minio as a client library.

It seems that minio is now in "maintenance mode", but it's not clear what's the state of their minio python library (at least, they are planning on a 8.0 release in the future).

I've opened an issue on their repo to ask for clarification about this.

[almet]

(they just answered saying it's currently actively maintained)