Bug 48290 - Implement ucr Variables for Ressource Management in systemd
Implement ucr Variables for Ressource Management in systemd
Status: NEW
Product: UCS
Classification: Unclassified
Component: General
UCS 4.4
Other Linux
: P5 normal (vote)
: UCS 5.0-0-errata
Assigned To: UCS maintainers
UCS maintainers
https://www.redhat.com/en/blog/world-...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-12-06 12:10 CET by Christian Völker
Modified: 2021-04-28 10:13 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018112921000611
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2018-12-06 12:10:57 CET
Memory leaking processes cause a system to use swap space (extremely slowing down the entire system) and finally falls into a out-of-memory situation.

The oom can not guarantee to kill the failing process which could lead into a system without important services.

Similar issue applies to a process hogging CPU.

systemd offers cgroups to limit the resource usage (see URL and https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-Managing_Services_with_systemd-Unit_Files#sect-Managing_Services_with_systemd-Unit_File_Modify)


Currently administrator has to set the desired values in file named "*.conf" in a (to be created manually) directory named "service.d" under  /etc/systemd/system

Would be great to have ucr variables and templates for these files to be created:
systemd/ssh/MemoryAccounting=(y/n)
systemd/ssh/MemoryLimit=1G

So global syntax could be
systemd/<SERVICE>/<VALUE>
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:30:39 CET
This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.