Decrease max_object_size for AIO #6

New issue

Closed

opened 2023-05-18 19:41:51 +00:00 by abereziny · 2 comments

abereziny commented

2023-05-18 19:41:51 +00:00

Member

Current value:

max_object_size: 67108864

It's too much for local playground due to fast space consumption which leads to constant requirement of AIO re-deployment.

Current value: ``` max_object_size: 67108864 ``` It's too much for local playground due to fast space consumption which leads to constant requirement of AIO re-deployment.

alexvanin commented

2023-06-28 12:53:49 +00:00

Owner

It's maybe too much for a test suit where objects must be bigger than max object size, but for the users there is pretty much no difference, I think.

Any more thoughts?

It's maybe too much for a test suit where objects _must_ be bigger than max object size, but for the users there is pretty much no difference, I think. Any more thoughts?

alexvanin commented

2024-07-11 14:18:28 +00:00

Owner

Seems like there is no much demand in changing this value right now. I suggest to keep default value as it is. There is a workaround by modifying this line and invoking make image-aio.

Seems like there is no much demand in changing this value right now. I suggest to keep default value as it is. There is a workaround by modifying [this](https://git.frostfs.info/TrueCloudLab/frostfs-aio/src/commit/f0c20be1b9c1918bd753bd5d477d97ff4fec5e2d/adm/frostfs-adm.yml#L4) line and invoking `make image-aio`.