Running an installation job
Submit a DataStax Enterprise install job to run on a cluster, datacenter, or node.
Submit a DataStax Enterprise install job to run on a cluster, datacenter, or node. An install job includes running a configuration job and by default, installing Java and the JCE Policy files required to enable unlimited strength encryption.
Lifecycle Manager pushes configuration jobs to a single
node at a time and restarts DataStax Enterprise on that node. For a newly added
cluster, the very first install job runs on several concurrent nodes. The
concurrency speeds the initial install process and is safe because the new cluster
cannot serve clients until it has been installed for the first time. After that,
install and configure jobs proceed one-node-at-a-time to ensure cluster
availability. The job does not progress to the next node until the current node
successfully restarts (that is, the node is responding on the
native_transport_port
). By default, the job gracefully stops
prematurely if a job fails for a single node. Jobs that are already running on nodes
are allowed to finish, but the job does not continue running on any remaining nodes
for that job. Doing so prevents any potential configuration problems from bringing
down multiple nodes, or even the entire cluster. If required, override this default
behavior with the Continue on error option, which will
attempt to run the job on all nodes, regardless of failure.
Install jobs that expand an existing cluster are throttled to one node at a time to prevent too much data from streaming concurrently.
Prerequisites
- All credentials (SSH and repositories) must be created, configuration profiles defined, and a cluster topology model built or imported before running any install jobs in Lifecycle Manager.
- LCM does not create data directories or manage their permissions on your behalf. If you want to use a custom data directory, please ensure that it exists and is owned by the cassandra user.
- An installed version of Python 2.6 through 2.7 is required on the target nodes. LCM does not automate the installation of Python. Install jobs fail if Python is not installed.