Job concurrency in Lifecycle Manager
Jobs run faster when more nodes are deployed concurrently during a job. Because nodes become unavailable at certain times during the deployment process, higher concurrency levels can interrupt service due to the inability of a cluster to respond to queries. The concurrency level options in the LCM job dialogs provide granularity for the aforementioned tradeoff. The following concurrency levels are available when running jobs at the cluster or datacenter level:
-
Automatic (safest but not always fastest): Default. Allows LCM to determine a safe concurrency level to use. Use this option when unsure which other option would be appropriate.
The Automatic option executes one job at a time, both for nodes in datacenters that were previously installed by LCM, and for nodes in new datacenters where an install job has not yet successfully completed. This behavior mirrors the Single node option.
-
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 datacenter (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.
|
Run jobs during off-peak hours if using a concurrency level that potentially or definitely interrupts service. |
Hover on a list option to view its tooltip description:
