Configure Linux systems not running systemd
Before you can configure workload management on Linux systems not running systemd, you must create a cgroup hierarchy in which splunkd and other system processes run in their own cgroups.
The following diagram illustrates the cgroup hierarchy on Linux systems not running systemd:
For more information, see cgroups.
Configure cgroups on non-systemd distributions
There are two ways to configure cgroups for workload management on Linux systems not running systemd:
Configure cgroups using cgconfig
You can use the cgconfig service installed with libcgroup to create cgroups on Linux systems not running systemd.
libcgroup is deprecated in RHEL 7.0 and other Linux distributions that support systemd.To configure cgroups for workload management using cgconfig:
- Check that
/sys/fsis mounted. If it is not mounted, mount thetmpfsin-memory filesystem under/sys/fs/cgroupas follows:sudo mount -t tmpfs -o size=10M tmpfs /sys/fsNote: Splunk Enterprise examines the/proc/mountsfile to determine whether your Linux machine can support workload management. - Create the
cgconfig.conffile under/etcand add the following contents:# Copyright IBM Corporation. 2007 # # Authors: Balbir Singh <balbir@linux.vnet.ibm.com> # This program is free software; you can redistribute it and/or modify it # under the terms of version 2.1 of the GNU Lesser General Public License # as published by the Free Software Foundation. # # This program is distributed in the hope that it would be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # # See man cgconfig.conf for further details. # # By default, mount all controllers to /cgroup/<controller> mount { cpuset = /sys/fs/cgroup/cpuset; cpu = /sys/fs/cgroup/cpu; cpuacct = /sys/fs/cgroup/cpuacct; memory = /sys/fs/cgroup/memory; devices = /sys/fs/cgroup/devices; freezer = /sys/fs/cgroup/freezer; net_cls = /sys/fs/cgroup/net_cls; blkio = /sys/fs/cgroup/blkio; } group splunk { perm { admin { uid = "splunk"; gid = "splunk"; } task { uid = "splunk"; gid = "splunk"; } } cpu { cpu.shares = "2048"; } memory { memory.limit_in_bytes = "3G"; } } - Restart the
cgconfigservice.# service cgconfig restart Stopping cgconfig service: [ OK ] Starting cgconfig service: [ OK ]This creates the
splunkcgroup.Note: The cgroup name must match the value ofworkload_pool_base_dir_namedefined inworkload_pools.confThe default value issplunk.
Configure cgroups using filesystem operations
To configure cgroups, the Linux admin, logged in as root user, must create the cgroups and assign the splunk user permissions to manage the cgroups, as follows:
- In the
workload_pools.conf.file, setworkload_pool_base_dir_nameto the root cgroup to be used by splunk. For example:[general] workload_pool_base_dir_name = splunkOr, send a POST request:
workloads/config/set-base-dirname -workload_pool_base_dir_name <base_dir_name>For endpoint details, see workloads/config/set-base-dirname in the Splunk Enterprise REST API Reference Manual.
- Create cpu and memory cgroups:
sudo mkdir /sys/fs/cgroup/cpu/<workload_pool_base_dir_name> sudo mkdir /sys/fs/cgroup/memory/<workload_pool_base_dir_name> - Assign the splunk user permissions to manage the respective cgroups:
sudo chown -R ${USER} /sys/fs/cgroup/cpu/<workload_pool_base_dir_name> sudo chown -R ${USER} /sys/fs/cgroup/memory/<workload_pool_base_dir_name>Note: If you have specified a user asSPLUNK_OS_USERinsplunk-launch.conf, you must specify the same user as {USER} in the command. For more information see splunk-launch.conf in the Splunk Enterprise ''Admin Manual''. - Assign CPU shares for
splunkcgroup:cd /sys/fs/cgroup/cpu/splunk echo 2048 > cpu.shares - Assign physical memory for the
splunkcgroup:cd /sys/fs/cgroup/memory/splunk/ echo 14G > memory.limit_in_bytes
Next step
After you set up cgroups on your Linux operating system, you can configure workload management in Splunk Enterprise. See Configure workload management.