Adjusting idle timeout values for LCM jobs

Adjust the default timeout values for Lifecycle Manager jobs as necessary for your environment.

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:
  • Installation job
  • Restarting a node during a job
  • Configuration job on a node
  • Importing a cluster job

opscenterd.conf

The location of the opscenterd.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/opscenterd.conf
  • Tarball installations: install_location/conf/opscenterd.conf

Procedure

  1. Open opscenterd.conf for editing.
  2. Adjust the available default idle timeout values in the [lifecycle_manager] section:
    [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: 120 seconds.
    [lifecycle_manager] node_configure_idle_timeout
    Duration of inactivity in seconds before marking a node configuration job as idle. Default: 120 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.
    The following example doubles the default timeout values for LCM jobs:
    [lifecycle_manager]
    node_install_idle_timeout = 1800
    node_restart_idle_timeout = 240
    node_configure_idle_timeout = 240
    node_cluster_import_idle_timeout = 240
    node_install_agent_idle_timeout = 240
  3. Restart OpsCenter.