Postgres and backup filesystems are over allocated by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Ovidiu Poncea |
Bug Description
Brief Description
-----------------
Currently postgres fs allocation is 40G for disk size greater than 240G and 20G for disk size between 240G - 186G inclusive by default. Now that OpenStack services are no longer part of the platform, this filesystem is greatly over-allocated. The default value should be cut in half:
20G for large disk size and 10G for small disk size by default.
The default backup filesystem should therefore be adjusted to 25G and 15G respectively to reflect the reduction of postgres fs allocation.
Severity
--------
Minor
Steps to Reproduce
------------------
N/A
Expected Behavior
------------------
Default filesystems are allocated optimally
Actual Behavior
----------------
Default Postgres and backup filesystems are not allocated optimally
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
Master
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
System Test
Changed in starlingx: | |
assignee: | nobody → Ovidiu Poncea (ovidiu.poncea) |
Changed in starlingx: | |
status: | New → In Progress |
For larger disks the allocation for the backup is ok, 25GB. For smal disks we need to set it to 20GB as the minimum is computed using a formula which is present in multiple parts of the code and I'm reluctant to change it.