Configuring SSH connection thresholds for LCM jobs

About this task

Adjust the default values for SSH connection attempts during Lifecycle Manager (LCM) jobs as necessary for your environment.


  1. Locate the opscenterd.conf configuration file. The location of this file depends on the type of installation:

    • Package installations: /etc/opscenter/opscenterd.conf

    • Tarball installations: install_location/conf/opscenterd.conf

  2. Open opscenterd.conf for editing.

  3. Adjust the available SSH connection values in the [lifecycle_manager] section:

    • [lifecycle_manager] ssh_connect_timeout_in_seconds

      The number of seconds to wait for the SSH server on a target node to respond to a connection attempt during an LCM job. Default: 30 seconds.

    • [lifecycle_manager] ssh_max_attempts

      The maximum number of times to attempt an SSH connection to a given target during an LCM job. Default: 3.

    • [lifecycle_manager] ssh_retry_delay_in_seconds

      The number of seconds to wait between SSH connection retries during an LCM job. Default: 10 seconds.

      The following example doubles the default values for SSH connection attempts by LCM:

      ssh_connect_timeout_in_seconds = 60
      ssh_max_attempts = 6
      ssh_retry_delay_in_seconds = 20
  4. Restart OpsCenter.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,