Incomplete and possibly incorrect documentation for cgroups, can't persist the settings at reboot

Edvin

Hi, I'm following the Using cgroups for resource control guide, and the Making the settings persistent at reboot is missing instructions for legacy systemv-based init scripts. Our DSS version is now 14.0.2, but we originally installed something pre-v13. Our nodes don't have the /etc/dataiku/ directory, but have /etc/init.d/dataiku.<NODE_TYPE>.

Based on the info here, I updated the /etc/init.d/dataiku.design script like this to persist the setup for cgroups v1 (I'm only showing the top of the script):

#!/bin/sh
# Boot time init script for Dataiku DSS

# chkconfig: 2345 90 10
# description: starts the Dataiku DSS

### BEGIN INIT INFO
# Provides:          dataiku.design
# Required-Start:    $local_fs $network
# Required-Stop:     $local_fs $network
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts the Dataiku DSS
### END INIT INFO

set -e

# Read configuration file, nothing to do if none
#
# Should contain following configuration variables:
# DIP_HOME=<installation directory>
# DIP_USER=<user account>
#
# May contain an optional list of cgroups to create for DSS use
# DIP_CGROUP_ROOT=<cgroup root mountpoint, if different from the default /sys/fs/cgroup>
# <colon-separated list of cgroup directories to create, relative to the cgroup root mountpoint>
DIP_CGROUPS="cpu/DSS:memory/DSS"

When I restarted our Design node EC2 instance, the cgroups directories I created manually (`/sys/fs/cgroup/memory/DSS` and /sys/fs/cgroup/cpu/DSS) were gone.

FYI here's how I created the directories:

sudo mkdir -p /sys/fs/cgroup/memory/DSS
sudo mkdir -p /sys/fs/cgroup/cpu/DSS
sudo chown -Rh dataiku:dataiku /sys/fs/cgroup/memory/DSS
sudo chown -Rh dataiku:dataiku /sys/fs/cgroup/cpu/DSS

We're using Amazon Linux 2 and cgroups v1.

Operating system used: Amazon Linux 2

Alexandru

Hi @Edvin ,
We see that you’ve raised a support ticket regarding this and will continue coordinating there.

For context, DSS 13.x used legacy System V init scripts (/etc/init.d/dataiku[.NAME]) for boot-time startup:
https://doc.dataiku.com/dss/latest/installation/custom/initial-install.html#optional-enable-startup-at-boot-time

In DSS 14+, instances need to be migrated to the systemd-based setup:

• Remove any legacy startup scripts.
• /etc/dataiku/INSTANCE_ID/dataiku-boot.conf
• Note that service configuration keys have changed from the legacy DIP_xxx syntax to DSS_xxx.

We’ll share any additional insights here once the support ticket is resolved.

Thanks