Adjust idle timeout values for LCM jobs
Adjust the default values for idle timeouts during Lifecycle Manager (LCM) jobs as necessary for your environment.
If jobs are timing out prematurely, increase the idle thresholds as appropriate for the job type, including installation jobs, restarting nodes during jobs, configuration jobs on nodes, and importing cluster jobs.
-
Locate the
opscenterd.conffile. The location of this file depends on the type of installation:-
Package installations:
/etc/opscenter/opscenterd.conf -
Tarball installations:
INSTALL_DIRECTORY/conf/opscenterd.conf
-
-
Open opscenterd.conf for editing.
-
Adjust the available default idle timeout values in the
[lifecycle_manager]section.The following example doubles the default timeout values for LCM jobs:
[lifecycle_manager] node_install_idle_timeout = 1800 node_restart_idle_timeout = 600 node_configure_idle_timeout = 600 node_cluster_import_idle_timeout = 240 node_install_agent_idle_timeout = 240-
[lifecycle_manager] node_install_idle_timeout: Duration of inactivity in seconds before marking an install job as idle. Default: 900 seconds.
-
[lifecycle_manager] node_restart_idle_timeout: Duration of inactivity in seconds before marking a node restart job as idle. Default: 300 seconds.
-
[lifecycle_manager] node_configure_idle_timeout: Duration of inactivity in seconds before marking a node configuration job as idle. Default: 300 seconds.
-
[lifecycle_manager] node_cluster_import_idle_timeout: Duration of inactivity in seconds before marking a cluster import job as idle. Default: 120 seconds.
-
[lifecycle_manager] node_install_agent_idle_timeout: Duration of inactivity in seconds before marking an agent install job as idle. Default: 120 seconds.
-