remove quota FIFO support

[harshavardhana]

No description provided.

[mshanmu]

@harshavardhana , This is very important feature. I would dare say a key differentiator. Any reason on why it is being removed?

[harshavardhana]

@harshavardhana , This is very important feature. I would dare say a key differentiator. Any reason on why it is being removed?

You need to use ILM instead of FIFO for expiring old content - this is not an important feature for any of our customers and it is not optimal.

If you are an active customer please reach out to https://subnet.min.io if not we are removing this.

[vadmeste]

Few comments

[mshanmu]

@harshavardhana , This is very important feature. I would dare say a key differentiator. Any reason on why it is being removed?

You need to use ILM instead of FIFO for expiring old content - this is not an important feature for any of our customers and it is not optimal.

If you are an active customer please reach out to https://subnet.min.io if not we are removing this.

@harshavardhana , Thanks for the reply !! IMO, they are not equivalent, functionality-wise. With FIFO support, MinIO automatically takes cares of deleting the oldest files as the bucket usage reaches the bucket quota limits. With an ILM rule, the user cannot specify that the oldest files in the bucket to be automatically deleted as the bucket usage reaches the bucket quota limits. Please correct me if I am wrong.

Btw, another suggestion, please create an issue so that users will be aware that this feature is being removed.

[harshavardhana]

@harshavardhana , This is very important feature. I would dare say a key differentiator. Any reason on why it is being removed?

You need to use ILM instead of FIFO for expiring old content - this is not an important feature for any of our customers and it is not optimal.

If you are an active customer please reach out to https://subnet.min.io if not we are removing this.

@harshavardhana , Thanks for the reply !! IMO, they are not equivalent, functionality-wise. With FIFO support, MinIO automatically takes cares of deleting the oldest files as the bucket usage reaches the bucket quota limits. With an ILM rule, the user cannot specify that the oldest files in the bucket to be automatically deleted as the bucket usage reaches the bucket quota limits. Please correct me if I am wrong.

ILM rule already provides necessary control. You can specifically set days based expiration on various prefixes.

We will be adding space based ILM expiration as an extension to S3 API in future.

FIFO in it's current form is broken, it doesn't work with really large namespaces where potentially crashes the server.

[parkjeongryul]

I've read the ILM document, and it seems that FIFO quata cannot be replaced.

If I want to delete old buckets by specifying a size (like 10Gi) as threshold instead of specific date, how can i replace it with ILM?

Is there a way to do this using ILM?

[harshavardhana]

I've read the ILM document, and it seems that FIFO quata cannot be replaced.

If I want to delete old buckets by specifying a size (like 10Gi) as threshold instead of specific date, how can i replace it with ILM?

Is there a way to do this using ILM?

Size based ILM will come in future, no ETA yet.