Running an upgrade job for a DSE patch version

After cloning a configuration profile with an updated DSE minor version, run an upgrade job on a datacenter or node. The upgrade job downloads and installs DSE and applies the values in the associated config profile.

After reviewing the DSE patch release upgrade docs and cloning a configuration profile with an updated DSE minor version, run an upgrade job on a datacenter or node.
Note: Upgrades are not allowed 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 to prepare a datacenter for upgrade or recovery afterward.
The upgrade job downloads and installs DSE and applies the values in the associated config profile.

Prerequisites

Procedure

  1. Click Clusters in the Lifecycle Manager navigation menu.
  2. Select the datacenter or node to run an upgrade on.
  3. Be sure to associate the cloned config profile with the datacenter or node being upgraded. Click Edit from the drop menu and select the config profile in the Edit Datacenter or Edit Node dialog to use for the upgrade.

    Select the cloned config profile for the upgrade in the Edit dialog

  4. Click Upgrade from the drop menu for the datacenter or node being upgraded.

    Upgrade drop menu in LCM Clusters page

    The Run Upgrade Job dialog appears.

    Run Upgrade Job for a Node view:

    Run Upgrade (DSE) Job dialog on nodes in LCM

    Run Upgrade Job for a Datacenter view:

    Run Upgrade (DSE) Job dialog on datacenter in LCM

  5. To override the default error behavior and continue running the job on subsequent nodes until all nodes are finished, select Continue on error. The job continues running despite encountering errors.
    By default, a job ceases running on additional nodes upon encountering an error on any given node. Any nodes that are already running continue to completion.
  6. Optional: Enter a Description about the upgrade job. For example: upgrade node from DSE 5.0.7 to 5.0.9. The description displays in the Jobs pages when Viewing job details.
  7. If running an upgrade job on a datacenter, select a Concurrency Level:
    Note: Concurrency Level is not applicable to node-level jobs.
    • Automatic (safest but not always fastest): Default. Lets LCM determine a safe concurrency level to use. Use this option when unsure which other option would be appropriate.
      Note: The Automatic option behaves similarly to the Single node option for nodes in datacenters that have previously been installed by LCM. For nodes in new datacenters where an install job has not yet been successfully completed, the Automatic strategy behaves similarly to the All nodes options, which are presumed to be safe options because nodes in a datacenter that has not yet finished being installed should not yet be servicing requests.
    • Single node: Executes job on one node at a time. Use this option when having more than one node offline at a given time would impact availability.
    • One node per DC: Executes job concurrently on at most one node per DC. Use this option if having a single node in each DC offline does not impact availability.
    • Single rack within a DC (might interrupt service): Executes job concurrently on nodes such that at most one rack has nodes down at a time. Use this option if having an entire rack within a DC offline does not impact availability.
    • One rack per DC (might interrupt service): Executes job concurrently on nodes such that at most one rack in each DC has nodes down at a time. Use this option if having an entire rack in each DC offline does not impact availability.
    • All nodes within a DC (interrupts service): Executes job concurrently on all nodes in a DC. Use this option if having all nodes in a DC offline is acceptable.
    • All nodes (interrupts service): Executes a job concurrently on all nodes in a cluster. Use this option if having all nodes in a cluster offline is acceptable.
  8. If running an upgrade job on a datacenter, enter a Batch Size if the default (10) is not appropriate for your environment or selected Concurrency Level.
    Increase the Batch Size value if:
    • the datacenter is large.
    • the selected Concurrency Policy makes many nodes eligible to run concurrently (such as the All nodes within a DC option).
    • the default Batch Size (10) results in job run times that are too long.
    • your environment can handle a larger number of nodes performing downloads and installs simultaneously without impacting network bandwidth or the LCM server.
    Note: Batch size takes effect only when a large number of nodes are eligible for concurrent deployment, such as with the All nodes concurrency policies. Batch size has no effect on jobs with the single-node concurrency policy or on node-level jobs.
  9. Click Submit.
    The job is submitted. A dialog informs you the job is in the queue to run.
  10. Click View Job Summary to navigate quickly to the Jobs page to monitor the job progress. Click Close if you do not want to immediately monitor the job and prefer to remain in the Clusters workspace.