dr_validate maximum scheduling priority is set incorrectly

Products

• Network Observability
• CA Performance Management

Issue/Introduction

Upgrading from DX NetOps 23.3.13 to 24.3.2 on RHEL 8. The maximum scheduling priority (ulimit -e) value for dradmin is set to 20 but should be 0.  The dr_validate.sh script appended the parameter 'dradmin - nice 0' to the bottom of /etc/security/limits.conf, however, even after reboot, the value is still 20.  How can we get the setting to stick to 0?

Environment

Dx NetOps Performance Management 24.x

Resolution

See: https://medium.com/@ahmedmansouri/understanding-process-priority-and-nice-in-linux-67d259f3e2f8

 

A nice value of 0 corresponds to a priority of 20

The "niceness" scale goes from -20 to 19, whereas -20 is the highest priority and 19 the lowest priority. The priority level is calculated as follows:
PR = 20 + NI

so Priority of 0 == 20 + -20 nice.
priority of 20 == 20 + 0 nice

 

So the value is set correctly