Job types in Lifecycle Manager

The following primary job types can be run on an model in the Lifecycle Manager topology for cluster, datacenter, and node models:

Install jobs

An install job downloads, installs, and configures supported DataStax Enterprise (DSE) versions on pre-launched instances. LCM efficiently skips work that is already completed. For example, DSE is not downloaded again if the correct version of DSE is already installed on a target node, but configure steps are performed if necessary. If a DSE package is already installed but is a different version than specified in the install job, the install job fails. Only an upgrade job supports installing a different DSE version.

Install jobs are idempotent operations and can be safely rerun, ensuring your cluster continues to operate according to your desired configuration. If a job fails, it can be re-run and LCM efficiently completes the remaining work. Prior to OpsCenter provisioning with LCM, manually removing all traces of DSE packages from the affected nodes was required after a failed provisioning attempt.

Configure jobs

A configure job pushes an associated configuration profile to the appointed nodes and restarts the cluster.

A configure job requires that an install job be run first. Running a configure job is not allowed until a cluster is converged by a prior install job.

Upgrade jobs

An upgrade job downloads and installs DSE and applies the values specified in the associated configuration profile. Upgrade jobs are only allowed at the datacenter and node levels. Upgrades cannot be run at the cluster level because there are frequently context-specific requirements about the order in which datacenters must be upgraded, and steps that must be performed outside LCM to prepare a datacenter for upgrade or recovery afterward.

Upgrades to a minor DSE release are supported within a release series. For example, upgrade to a higher patch version within 6.0, 6.7, or later major versions.

Skipping patch versions during an upgrade is supported. For instance, upgrade from 6.0.0 to 6.0.4. Review the DSE Upgrade Guide to determine which patch version to upgrade to, to plan any required configurations that must be deployed using LCM prior to an upgrade, and to become aware of any steps that must be performed outside of LCM during the upgrade.

During the cloning configuration profile process when a new DSE version is selected, LCM provides complete details on which configuration profile settings have been added, removed, or had their default settings changed. The notifications also inform you of user-supplied custom values that are still valid and preserved.

Version downgrades of DataStax Enterprise are not supported within Lifecycle Manager.

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,