File bug-1066710_pacemaker-pacemaker.service-TasksMa... of Package pacemaker.23975

Overview Repositories Revisions Requests Users Attributes Meta

File bug-1066710_pacemaker-pacemaker.service-TasksMax=infinity.patch of Package pacemaker.23975

commit 91393d471b2e0a8d015aae6b61d4b2883985f47b
Author: Gao,Yan <ygao@suse.com>
Date:   Fri Nov 10 12:33:02 2017 +0100

Doc: pacemaker.service: Recommend not to limit tasks
    
    Systemd v227 introduced the "pids" cgroup controller:
    https://github.com/systemd/systemd/commit/03a7b521e
    
    From systemd v228, it's enabled for all services by default, and the
    global default of TasksMax was 512:
    https://github.com/systemd/systemd/commit/9ded9cd14
    
    The limit could be be easily hit since any processes/threads spawned
    from the unit count, such as the "ocf" type of resources.
    
    In systemd v235, the default TasksMax= has been effectively changed to
    4915:
    https://github.com/systemd/systemd/commit/79baeeb96
    
    But it still could be a potential issue for cluster with heavy workload.
    
    Generally it probably doesn't make much sense to set such a limit for a
    resource manager like pacemaker.
    
    This commit recommends the same as the docker project does:
    https://github.com/moby/moby/commit/33a8ab29ed

diff --git a/mcp/pacemaker.service.in b/mcp/pacemaker.service.in
index 8ebadc637..516de0f82 100644
--- a/mcp/pacemaker.service.in
+++ b/mcp/pacemaker.service.in
@@ -41,6 +41,10 @@ SuccessExitStatus=100
 
 ExecStart=@sbindir@/pacemakerd -f
 
+# Uncomment TasksMax if your systemd version supports it.
+# Only systemd v227 and above support this option.
+#TasksMax=infinity
+
 # If pacemakerd doesn't stop, it's probably waiting on a cluster
 # resource.  Sending -KILL will just get the node fenced
 SendSIGKILL=no

Places

File bug-1066710_pacemaker-pacemaker.service-TasksMax=infinity.patch of Package pacemaker.23975

Places