cass-operator icon indicating copy to clipboard operation
cass-operator copied to clipboard

The DataStax Kubernetes Operator for Apache Cassandra

Results 209 cass-operator issues
Sort by recently updated
recently updated
newest added

**What this PR does**: Creates a new option that does rolling restart outside cads-operator's controller. **Which issue(s) this PR fixes**: Fixes #385 **Checklist** - [x] Changes manually tested - [x]...

**What is missing?** At the moment, to do a rolling restart, we must modify the CassandraDatacenter spec. We want a task that would do the same without requiring the modification...

enhancement
zh:Ready-For-Review

Nodes should be decommissioned in a deterministic, balanced, way. We should always choose the rack with the most nodes up and ready compared to the target size. If the number...

enhancement

**What happened?** I manually edited the StatefulSet annotations to cause rolling restart (same way as kubectl rollout restart would do). First pod was started correctly again and got to 2/2...

bug

**What is missing?** When adding nodes to a cluster or creating a new cluster we can end up in a state where we do not bootstrap nodes in a balanced...

enhancement

When many tables are present in a cluster, the metrics pipeline can fail due to timeouts, overfull metrics reservoirs, and other issues that arise at the edge of MCAC's design...

zh:Ready
Epic

**What is missing?** When a CassandraTask targets more than a single pod, it executes tasks in parallel on all pods. We need more fine-grained execution orders, e.g. if a task...

enhancement

**What is missing?** At the moment, it is possible for us to start replacing more nodes than the cluster can in reality handle. This is because we continue with the...

enhancement

**What happened?** After requesting a rolling restart on a datacenter with 3 Cassandra nodes, cass-operator restarts the `-sts-2` pod and sometimes a few seconds later `-sts-1` gets terminated by cass-operator,...

bug
assess

**What is missing?** When setting `spec.replaceNodes` cass-operator will set it to `sepc.replaceNodes = []` after it has started replacing nodes. I would like `cass-operator` to not do that. https://github.com/k8ssandra/cass-operator/blob/9c4c3692a90b0199ab002f23fcb08791bf7d7276/operator/pkg/reconciliation/reconcile_racks.go#L1078-L1080 **Why...

enhancement
assess