Who provides enterprise support for Cassandra?
Three groups do. IBM supports DataStax Enterprise, HCD and Astra, and its page lists Apache Cassandra under IBM Elite Support. Managed-service providers and the cloud vendors support their own services. Independent providers such as AceMQ support the Apache Cassandra you run on any infrastructure, 24/7, with response targets from 15 minutes, by plan. Which one you need follows where Cassandra runs and which version you use.
What does 24/7 Cassandra support cover with AceMQ?
Cover is around the clock, with response from 15 minutes on the fastest plans. Example Sev 1: writes fail with UnavailableException while nodetool status shows every node up. An engineer joins you, checks consistency level against live replicas, and delivers a written cause. P2 1 hour, P3 4 hours, P4 next business day.
Does AceMQ support DataStax Enterprise as well as Apache Cassandra?
Yes, at the Cassandra layer: data model, repair, compaction, GC, topology and upgrades. DSE-only features and product defects stay with the vendor, and we work that escalation with you. Many teams keep the vendor licence for DSE features and add independent cover for operations.
Which Cassandra versions does AceMQ support?
Apache Cassandra 3.11, 4.0, 4.1 and 5.0, DSE, and the Cassandra layer on Amazon Keyspaces and Azure Managed Instance for Apache Cassandra. The Apache download page lists 5.0.9, 4.1.12 and 4.0.21 as released on 7 August 2026 and does not list 3.11. We support 3.11 and plan its upgrade to 4.x or 5.0 on your calendar.
Why do my Cassandra reads time out after we delete a lot of data?
Because a delete writes a tombstone that every read of that partition scans until it ages past gc_grace_seconds and compaction removes it. Heavy deletes or short TTLs make reads progressively slower, and a read that passes tombstone_failure_threshold is aborted. We fix it in layers: relief through targeted compaction, a repair schedule that finishes, then a data model that stops producing the tombstones. The full mechanics are in the repair, compaction and tombstones guide.
Why do deleted rows come back in Cassandra?
Deleted rows return when a node missed the tombstone and the tombstone was purged before repair reached it. We check gc_grace_seconds against your repair cadence, run repair on the affected ranges and set a schedule that finishes inside that window.
Can you help us upgrade from Cassandra 3.11 to 4.x or 5.0?
Yes. The upgrade is a sequenced rolling restart: nodes on different majors cannot stream, so no bootstrap, decommission or repair runs until the whole ring is done. We rehearse on a clone, check driver compatibility, upgrade SSTables node by node and keep a tested rollback point. The route is written up in the 3.11 to 5.0 upgrade path.
Can you fix Cassandra performance problems without adding nodes?
Usually. Most performance problems are data model problems seen at scale, such as one partition growing to gigabytes, tombstones from queue-like deletes or a compaction strategy that no longer matches the workload. Others are settings: heap and GC, repairs colliding with peak load, or a consistency level that waits on the slowest replica. We diagnose from metrics and histograms and say plainly when the answer is more nodes.
Can AceMQ support Cassandra for a client under DORA?
Yes. The contract states response targets by severity, 24/7 cover, incident assistance and a written root cause analysis after every P1. DORA does not certify suppliers, so the compliance judgement stays with you or your integrator. See Cassandra support under DORA.
What does a Cassandra health check include?
Token ownership and load per node, replication and consistency settings against your durability needs, GC pause distribution, compaction backlog and SSTable counts, repair completion history against gc_grace_seconds, partition size distribution, and a capacity projection. It ends with a risk-ranked plan. Quotes are answered within 1 hour.
Who offers Cassandra consulting and professional services?
Cassandra consulting comes from IBM and its partners for DataStax products, from managed-service providers for their own platforms, and from independent firms such as AceMQ for the clusters you run. AceMQ consults on any Cassandra version and any deployment, with the same engineers who staff the 24/7 rota, which is why a recommendation comes with the context of how the cluster behaves in an incident. See Apache Cassandra consulting for engagement formats.
Can AceMQ take on one Cassandra project without an annual deal?
Yes. A data model review, a 3.11 to 4.x upgrade or a repair strategy rebuild can be scoped as its own work. If the cluster needs ongoing attention afterward, an annual agreement adds 24/7 response and keeps the same engineers on your account.
What determines how much Cassandra support costs?
Typical annual contracts are $24,000 to $72,000 (USD). The main inputs are node and datacenter count, Apache Cassandra versus DSE, consistency and repair requirements, planned upgrades, and the response plan. Describe the ring in a request and we send a quote within 1 hour.