High CPU usage by opscenterd
Increasing the nodelist polling period or setting a sleep delay can reduce excessive CPU usage when starting or running opscenterd.
Increasing the nodelist polling period or setting a sleep delay can reduce excessive CPU usage when starting or running opscenterd. In some environments, you might notice CPU usage for the opscenterd spiking dramatically (almost to 100%) upon startup or while it's already running. Typically, this is caused by the retrieval and parsing of cluster topology performed during startup and every 60 seconds by default while opscenterd is running. When OpsCenter is managing multiple clusters with vnodes enabled, the impact of this CPU spike can cause performance issues or even stop opscenterd from starting up properly.
Configuring the polling period for CPU issues while running opscenterd
Increasing the nodelist polling period can reduce CPU usage when running opscenterd.
cluster_name.conf
The location of the cluster_name.conf file depends on the type of installation:
- Package installations: /etc/opscenter/clusters/cluster_name.conf
- Tarball installations: install_location/conf/clusters/cluster_name.conf
- Windows installations: Program Files (x86)\DataStax Community\opscenter\conf\clusters\cluster_name.conf
Increasing the nodelist polling period can reduce CPU usage when running opscenterd.
The nodelist_poll_period
configuration option is applicable to
OpsCenter version 5.0.2+.
Procedure
Configuring a sleep delay for CPU issues when starting opscenterd
Configuring a delay between clusters during startup helps alleviate opscenterd CPU usage on startup, allowing OpsCenter to function properly.
opscenterd.conf
The location of the opscenterd.conf file depends on the type of installation:
Location | Package | Installer (GUI or text mode) | Tarball | |
---|---|---|---|---|
Service | No-service | |||
/etc/opscenter/opscenterd.conf | X | X | ||
install_location/conf/opscenterd.conf | X | X |
Configuring a delay between clusters during startup helps alleviate opscenterd CPU
usage on startup, allowing OpsCenter to function properly. The
startup_sleep
configuration option is applicable to OpsCenter
version 5.1.1+.