DataStax Enterprise Operations

DataStax Mission Control is current in Private Preview. It is subject to the beta agreement executed between you and DataStax. DataStax Mission Control is not intended for production use, has not been certified for production workloads, and might contain bugs and other functional issues. There is no guarantee that DataStax Mission Control will ever become generally available. DataStax Mission Control is provided on an “AS IS” basis, without warranty or indemnity of any kind.

If you are interested in trying out DataStax Mission Control please contact your DataStax account team.

Interactions with DataStax Mission Control are broadly categorized as declarative or imperative. Use declarative APIs to define a desired end-state and DataStax Mission Control constantly takes steps to achieve that goal. For example, handle the definition of a DataStax Enterprise cluster or datacenter through declarative APIs because these are long-lived resources that require reconciliation. In comparison, imperative APIs describe a singular operation or task to be run to completion with an associated status. Imperative APIs within DataStax Mission Control include operational tasks on a specified cluster, such as performing a rolling restart.

Declarative or imperative operations are performed at either the cluster or the datacenter level.

Cleanup: Run the nodetool cleanup command for specific keyspaces on all nodes in a particular datacenter (DC).
Rebuild: Run the nodetool rebuild command across a datacenter to populate data by streaming from another (source) datacenter (DC).
Replace a DSE node: Replaces an existing node with a new, empty pod owning the same token ranges.
Rolling Restart: Restart all nodes in a cluster in a rolling fashion while applications continue to run with zero downtime.
Upgrade SSTables: Upgrade all SSTables to newer formats where required.