Platform components and operations

The Mission Control operator manages custom resources and cluster operations, specifically handling the creation and management of database clusters across various hosting options. Additional resources might be needed for managing complex cluster configurations.

The Mission Control operator reconciles custom resources automatically, particularly during cluster creation or configuration changes like adding nodes or modifying cluster settings.

Review the operator logs in the mission-control-operator pod for specific errors and check resource creation. Verify that the service account has the necessary permissions as described in the Service account permissions documentation. Two main types of issues may affect the mission-control-operator: reconciliation failures and resource quota problems.

Resource creation issues may stop the mission-control-operator from functioning properly, especially when deploying new clusters or performing operations like node replacements. Review the resource creation logs in the mission-control-operator pod and check resource quotas in the target namespace. Verify that the service account has the necessary permissions to create resources in the target namespace. Monitor the cluster creation process through the Mission Control UI or API to identify any issues early, particularly during operations like backup/restore or rolling restarts. If issues persist, contact DataStax support for assistance.

The cass-operator manages the lifecycle of all Apache Cassandra®, DataStax Enterprise (DSE), and Hyper-Converged Database (HCD) logical datacenters. Additional resources might be needed for managing multiple clusters.

The operator reconciles database resources through these automated steps:

The operator may experience two main types of issues: reconciliation failures and resource quota problems. Reconciliation failures occur due to resource constraints or configuration issues during automated operations like rolling restarts, node replacements, or datacenter additions. When this happens, review the operator logs in the cass-operator pod for specific errors and check the resource quotas. Verify that the service account has the necessary permissions as described in the Service account permissions documentation.

You may encounter resource quota issues when you manage multiple clusters across different environments. To resolve these issues, review and adjust the resource quotas in the Kubernetes namespace where Mission Control is deployed. Look for resource leaks after operations like backup/restore or node replacements fail. Monitor resource utilization regularly through the Mission Control dashboards to identify these issues early.

The k8ssandra-operator manages the lifecycle of all K8ssandra resources including cluster definitions, Reaper, and Medusa components. Additional resources might be needed for managing complex cluster configurations.

The operator reconciles K8ssandra resources automatically, particularly during cluster creation or configuration changes like adding nodes or modifying cluster settings.

Review the operator logs in the k8ssandra-operator pod for specific errors and check resource creation. Verify that the service account has the necessary permissions as described in the Service account permissions documentation. Common reconciliation issues include failed cluster provisioning and configuration validation errors during operations like cluster upgrades or datacenter modifications.

Resource creation issues can prevent the operator from functioning properly, especially when deploying new clusters or performing operations like node replacements. Review the resource creation logs in the operator pod and check resource quotas in the target namespace. Verify that the service account has the necessary permissions to create resources in the target namespace. Monitor the cluster creation process through the Mission Control UI or API to identify any issues early, particularly during operations like backup/restore or rolling restarts. If issues persist, contact DataStax support for assistance.

The kube-state-metrics component monitors the state of various Kubernetes resources and makes them available for monitoring and alerting.

Review the metrics logs in the kube-state-metrics pod for specific errors and check resource quotas. Verify that the service account has the necessary permissions as described in the Service account permissions documentation. Common issues include collection failures and resource quota problems during high-volume operations.

Resource quota issues can prevent the component from functioning properly, especially when collecting metrics from large clusters. Review the resource quotas in the target namespace and adjust them if necessary. Monitor the metrics collection process through the Mission Control dashboards to identify any issues early. If issues persist, contact DataStax support for assistance.

Loki is the log aggregation system for Mission Control. It collects and stores logs from all platform components and database nodes.

Mimir is the metrics storage and query system for Mission Control. It provides long-term storage and efficient querying of metrics collected from all platform components and database nodes.

The aggregator component controls Vector for metrics aggregation in Mission Control. It collects metrics from all platform components and database nodes and forwards them to Prometheus.

Medusa is the backup and restore system for Mission Control. It provides point-in-time backup and restore capabilities for database clusters.

For detailed information about Medusa configuration and usage, see Backup and restore.

Reaper is the repair management system for Mission Control. It provides automated repair scheduling and execution for database clusters.

For detailed information about Reaper configuration and usage, see Repair management.