Apache Cassandra support, 24/7

Cassandra Support for Self-Run Clusters, DataStax Enterprise and Multi-Datacenter Rings

Last reviewed by Tyler Eastridge

AceMQ supports Apache Cassandra 24/7 on the clusters you run: self-managed rings, DataStax Enterprise, multi-datacenter topologies and Kubernetes. Most calls start with one of three problems: read timeouts caused by tombstones, nodes that flap because of garbage collection pauses, or repairs that never finish inside gc_grace_seconds and let deleted data come back.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Apache Cassandra consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Cassandra problems we fix every week

Tombstones, flapping nodes, uneven load and failed bootstraps, each with the nodetool output or log we read before changing anything.

Common Apache Cassandra production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Reads time out on a table with many deletes or short TTLsRead X live rows and Y tombstone cells warnings in system.log, nodetool tablestats for tombstones per slice, and the table's gc_grace_secondsTime-bucketed partitions, compaction that matches the delete pattern, thresholds left at their defaults so the problem stays visible
A node is marked down, then up, with a healthy networkGC log pause lengths against the gossip failure detector window, then nodetool tpstats for blocked native-transport threadsFix the wide partition or large read filling the heap, then size the heap and collector
One node carries far more load than its peersnodetool status ownership, nodetool tablehistograms for partition size, and the partition key's real cardinalityA bucketing component in the key and a backfill, not more nodes
Deleted rows reappearnodetool repair completion history per table against gc_grace_seconds, and whether a replica was down longer than max_hint_windowA repair schedule that finishes with margin, plus a repair of the affected ranges
UnavailableException while every node shows UNThe keyspace's replication settings against the datacenter names the snitch reports, and the consistency level the driver usesCorrect the NetworkTopologyStrategy datacenter names, then the driver's local datacenter setting
Bootstrap or nodetool decommission fails halfwaynodetool describecluster for schema disagreement, streaming throughput, stream timeouts on large partitionsResolve schema agreement first, then restart the stream with sized timeouts
Compaction never catches upnodetool compactionstats pending tasks, SSTable count per table, compaction strategy against the workloadTWCS for time series, LCS for read-heavy tables, throughput raised only after strategy is right
The cluster stays slow for hours after an outageHinted handoff backlog, read repair rate, and whether the outage exceeded max_hint_windowThrottle hint replay, run a repair where hints were dropped

Each P1 ends with a written cause naming the table, node or setting responsible.

Reads timing out or a node that keeps dropping? Ask for a quote and a Cassandra engineer replies within the hour.

Contact Us

Deployment coverage

Which Cassandra deployments does AceMQ support, and who covers what?

AceMQ supports the Cassandra you run, on the version you run, wherever it runs. The table shows what we cover, what the platform or product vendor covers, and what neither of us covers.

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Apache Cassandra 3.11, 4.0, 4.1 and 5.0, self-managed (VMs, bare metal)24/7 incident response, written RCA on P1s, data model review, repair and compaction schedules, JVM and GC work, rolling upgrades, CVE advice for your versionThe Apache project publishes releases and offers community help; it offers no response commitment (cassandra.apache.org, read 17 Nov 2026)Application code is reviewed, not rewritten; hardware faults outside the agreed scope
DataStax Enterprise (DSE)The Cassandra layer: data model, repair, compaction, GC, topology, upgrade planning and migration planningIBM sells DataStax products; DSE-only features and product defects stay with the vendor (IBM Community post, 3 Oct 2025, read 17 Nov 2026)A patched DSE binary; DSE-only components we cannot change
Amazon KeyspacesData model, partition and consistency design, driver retry and timeout settings, cost model for wide partitionsAWS runs and supports the service itself (aws.amazon.com/keyspaces)Platform faults and service limits set by AWS; compaction and repair are not exposed
Azure Managed Instance for Apache CassandraThe Cassandra layer inside the service: tables, consistency, client behaviour, upgrade timingMicrosoft supports the Azure service and its control planeAzure platform faults; settings the service does not expose
K8ssandra and Cass Operator on Kubernetes or OpenShiftPod and storage behaviour as it affects the ring: PVC performance, rolling restarts, repair scheduling through Reaper, resource limits against heap and off-heap memoryThe Kubernetes distribution vendor supports the platform; the operator project supports its own code through the communityControl-plane faults; operator versions their maintainers no longer publish
Multi-datacenter across AWS, Azure, GCP and on premisesSnitch and topology settings, LOCAL_QUORUM semantics, cross-datacenter repair, adding and removing a datacenter liveThe cloud providers support their networks and instancesInter-region network faults

Support options

Who provides enterprise support for Cassandra? Vendor and independent support compared

Enterprise support for Apache Cassandra comes from three places: IBM for DataStax products, managed-service providers for their own services, and independent providers such as AceMQ for the clusters you run yourself. The Apache project itself has no support contract.

IBM (DataStax) / Apache project (community)
AceMQ independent support
CoversIBM (DataStax): DataStax Enterprise, HCD and Astra; the IBM page lists Apache Cassandra under IBM Elite SupportApache project (community): Apache Cassandra releases; help on mailing lists and Slack
CoversApache Cassandra 3.11 to 5.0, DSE, and the Cassandra layer on Keyspaces and Azure
Contract after the IBM changeIBM (DataStax): IBM states that sales moved to IBM paper and existing customers keep the same level of support (IBM Community, 3 Oct 2025)Apache project (community): None
Contract after the IBM changeOne contract, plan set by SLA, scope and deployment
Maintained release linesIBM (DataStax): Per IBM lifecycle pagesApache project (community): 5.0.9, 4.1.12 and 4.0.21 are listed (7 Aug 2026); 3.11 is not listed on the download page (cassandra.apache.org/_/download.html, read 17 Nov 2026)
Maintained release linesSupport for the version you run, 3.11 included
Product defectsIBM (DataStax): IBM can fix its own DSE buildsApache project (community): Fixed through the project's release process
Product defectsWe diagnose, write the reproduction and work the escalation; we cannot ship a patched DSE binary
PriceIBM (DataStax): Set by IBM quoteApache project (community): Free
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

Short note under the table: if you depend on DSE-only features, keep the IBM licence and add independent cover for the operational layer. If you run Apache Cassandra, the vendor packages do not attach to your build, so independent support is the practical choice. Our buyer's guide walks through the eight questions to ask: How to choose Cassandra support after DataStax.

Something changed?

On DataStax or IBM Cassandra support? Start here

Each guide says what changed, who it affects and what to decide first.

What's Included

Everything in your Apache Cassandra support contract

Data model review, compaction and repair, JVM tuning and upgrades are covered together for Apache Cassandra, DSE and Kubernetes deployments.

  • 01

    Emergency Incident Response

    Nodes down, reads timing out, a ring that won't converge, or a bootstrap stuck mid-stream. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the data model, compaction, or repair change that prevents recurrence. Delivered as standard, not on request.

  • 03

    Data Model Review

    Partition key and clustering column design against your real access patterns, partition size distribution, and the delete and TTL patterns that quietly manufacture tombstones faster than compaction can remove them.

  • 04

    Compaction & Repair Strategy

    Compaction strategy matched to workload — TWCS for time series, LCS for read-heavy, STCS where it genuinely fits — plus a repair schedule that completes inside gc_grace_seconds rather than merely existing in cron.

  • 05

    JVM & GC Tuning

    Heap sizing, G1 versus ZGC selection for your pause budget, and off-heap memory accounting. We tune GC after fixing what is filling the heap, because the reverse order just moves the outage later.

  • 06

    Upgrades, Multi-DC & Migrations

    Rolling upgrades across 3.11, 4.x, and 5.0, adding or retiring a datacenter without downtime, and migrations to or from DataStax Enterprise, Amazon Keyspaces, and ScyllaDB.

Why AceMQ

What Cassandra teams get from AceMQ

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your keyspace layout, your replication factors, and your compaction choices — so a P1 call opens with a hypothesis rather than a tour of your ring.

  • No First-Line Triage Layer

    You reach a senior Cassandra engineer directly by phone, email, or Slack. No help desk collecting details to relay, and no escalation approval between you and someone who can read a GC log and a tablehistogram.

  • We Treat Data Model Issues as Data Model Issues

    Most Cassandra production pain traces back to partition key design and delete patterns. We will say when the answer is a model change and a backfill rather than more nodes — even though more nodes would be the easier recommendation to make.

  • Multi-DC Without the Guesswork

    Cross-datacenter replication, LOCAL_QUORUM semantics, snitch and topology configuration, and adding or retiring a DC live. This is where consistency mistakes hide until the day one region becomes unreachable.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am node flap is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Full-Stack, Not Just the Ring

    We diagnose across the driver's load balancing and retry policy, the JVM, storage latency, network policy, and Kubernetes. Cassandra symptoms frequently originate in the client or the disk rather than in Cassandra.

Cassandra environments we cover

Single and multi-datacenter rings, K8ssandra on Kubernetes, DataStax Enterprise, managed Cassandra services and sites with no outbound access.

  • Apache Cassandra 3.11, 4.x, 5.0
  • DataStax Enterprise (DSE)
  • Amazon Keyspaces
  • Azure Managed Instance for Apache Cassandra
  • K8ssandra & Cass Operator on Kubernetes
  • OpenShift
  • Multi-DC across AWS, Azure, and GCP
  • AWS (EC2, EKS) with instance-store or EBS
  • ScyllaDB migrations
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Hybrid cloud

Version coverage

Apache Cassandra versions we support

AceMQ supports the version you run. The table pairs each line with its latest Apache release and what we do on it.

Apache Cassandra versions we support
Cassandra versionLatest Apache releaseApache status on the download pageWhat AceMQ does on it
5.05.0.9, 7 Aug 2026Maintained until the 8.0 release24/7 support; the target for upgrades from 3.11 and 4.x
4.14.1.12, 7 Aug 2026Maintained until the 7.0 release24/7 support, including terms written to be read against DORA
4.04.0.21, 7 Aug 2026Maintained until the 6.0 release24/7 support and a rehearsed rolling upgrade to 4.1 or 5.0
3.11Not listed on the download pageNot listed24/7 support, with the upgrade sequenced and rehearsed before an incident forces it

Source: cassandra.apache.org/_/download.html, read 17 November 2026. Nodes on different major versions cannot stream to each other, so bootstraps, decommissions and repairs wait until the ring is upgraded. Step-by-step: Cassandra 3.11 to 5.0 upgrade path.

In practice

Cassandra support terms you can read against DORA

The EU Digital Operational Resilience Act (Regulation 2022/2554) has applied since 17 January 2025, and Article 30 sets what ICT supplier contracts contain. AceMQ's Cassandra contract states response targets by severity, 24/7 cover, incident assistance and a written root cause analysis after every P1. DORA certifies no supplier, so the compliance judgement stays with you or your integrator. Checklist: Cassandra support under DORA.

DORA

Cassandra support terms you can read against DORA

The EU Digital Operational Resilience Act (Regulation 2022/2554) has applied since 17 January 2025. Financial entities must hold written contracts with the ICT suppliers behind their systems, and Article 30 sets what those contracts contain. DORA certifies no supplier, so the responsibility stays with you.

  • Written response targets

    Response targets by severity are in the contract, by plan: from 15 minutes for P1, 1 hour for P2, 4 hours for P3 and the next business day for P4, around the clock. That gives you the measurable service levels Article 30 asks for.

  • Incident assistance and a written RCA

    A senior engineer joins the incident bridge, and every P1 closes with a written root cause analysis you can attach to your own incident record. There is no per-incident charge for calling us.

  • Named engineers and a clear scope

    The same senior engineers stay on your account, and the contract states which clusters, versions and environments are covered.

AceMQ for financial services

A request we see

When the integrator has no Cassandra team

A systems integrator asked AceMQ for 24/7 support of Apache Cassandra 4.1 for its telecom client in the EU, a client with DORA obligations. The integrator had no in-house Cassandra team.

  • The gap

    The integrator answers to its client for availability but, by its own account, does not have the Cassandra skills in its team to back that up.

  • The ask

    24/7 support for Cassandra 4.1, for a client with DORA obligations and a need for written response times.

  • What it takes

    A 24/7 rota of senior Cassandra engineers, response times by severity in writing, and a written RCA after every P1.

The integrator and its client are not named.

Consulting

Cassandra consulting and professional services

AceMQ delivers Cassandra consulting as fixed, named deliverables, each with a written report. Most engagements start with an assessment and end with a runbook your team keeps.

Cassandra consulting and professional services
DeliverableWhat you receive
Cluster health checkToken ownership and per-node load, replication factor and consistency review against your durability needs, GC pause distribution, compaction backlog, repair completion against gc_grace_seconds, and a risk-ranked roadmap
Data model and partition reviewEvery query inventoried, partition keys checked against real cardinality, bucketing and denormalisation recommendations, partition-size guardrails with monitoring
Upgrade planVersion and driver inventory, a rehearsal on a cloned cluster, a node-by-node sequence with a tested rollback point, post-upgrade checks
Performance tuningCompaction strategy per table, JVM and collector settings, repair pacing, read and write path analysis from the metrics, not from guesses
Multi-datacenter designSnitch and replication layout, LOCAL_QUORUM behaviour, adding or retiring a datacenter, failure scenarios tested on paper before production
Migration planningMoves to or from DataStax Enterprise, Amazon Keyspaces and ScyllaDB, with a dual-write and backfill path where a write freeze is not possible

Escalation Path

Your first hour of an Apache Cassandra outage

When reads time out on a healthy cluster, the person answering looks at tombstones and compaction first, not at adding nodes.

  1. From 15 min (by plan)first responseEmergencyProduction outage: writes failing with Unavailable errors, nodes down beyond quorum, or a data center unreachable
  2. 1 hourfirst responseCriticalSerious degradation: read timeouts from tombstones, a node cycling between up and down, compaction far behind
  3. 4 hoursfirst responseHighHot partitions on one node, deleted rows reappearing, a failed bootstrap or decommission
  4. Next Dayfirst responseStandardData model review, repair scheduling, compaction strategy choice, JVM settings and upgrade planning

Response clocks follow your plan, so a ring losing quorum is handled before a compaction question.

Need a named Cassandra engineer who knows your keyspaces and data centers? Request a quote or message us.

Contact Us

Pricing

What does AceMQ Apache Cassandra support cost?

Cassandra support commonly sits between $24,000 and $72,000 a year. It scales with node and datacenter count, Apache or DSE, how much upgrade and repair work is expected, and your response plan.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract spanning other technologies can earn a multi-technology discount.

Support In Practice

Cassandra cluster problems we have solved

Typical Cassandra engagements from AceMQ. Each card links to the full write-up: the ring, what the engagement assesses or changes, and what it delivers.

  • Support

    Cassandra Repair and Compaction Support

    Global Payments Processor

    Ongoing support for anti-entropy repair that never completed within gc_grace_seconds, leaving the cluster exposed to deleted data resurrecting.

    Apache CassandraReaperPrometheusKubernetes
  • Consulting

    Cassandra Data Model and Partition Design Consulting

    Digital Identity Services Provider

    Redesigning partition keys and clustering order to eliminate unbounded partitions and remove secondary index queries that were hitting every node.

    Apache CassandraKubernetesKafkaPrometheus
All use cases

Support options

Four tiers of Apache Cassandra support.

AceMQ offers Cassandra cover in four options, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for rings your team runs, proactive monitoring that finds wide partitions, tombstones and missed repairs first, managed Cassandra on your own infrastructure, and fully managed Cassandra on AceMQ infrastructure. Cassandra 3.11 to 5.0 and DataStax Enterprise are covered in all four.

  • Tier 1

    Apache Cassandra 24/7 Support & Incident Management

    Your team runs the ring, we handle escalations

    Best for: Teams operating Cassandra themselves who want a senior engineer for timeouts, repair or node trouble.

  • Tier 2

    Apache Cassandra 24/7 Support with Proactive Monitoring

    Scheduled model, repair and compaction reviews

    Best for: Teams that want tombstone buildup, repair gaps and hot partitions found in a review rather than in production.

  • Tier 3

    Managed Apache Cassandra on Your Infrastructure

    We operate your Cassandra rings on your hosts

    Best for: Organizations needing the ring inside their own data centers or cloud accounts, with AceMQ handling the daily upkeep.

  • Tier 4

    Fully Managed Apache Cassandra on AceMQ Infrastructure

    AceMQ runs the ring and its repairs for you

    Best for: Product teams that depend on Cassandra but do not want to staff an in-house operations group.

FAQ

Apache Cassandra support questions

Still have questions about Apache Cassandra? Email an Expert

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.

Let's talk

Find the Repair That Never Finished Before Your Next Delete Does

Send us your Cassandra version, datacenter layout and the last nodetool repair history you have. We reply to quote requests within 1 hour.

A senior Apache Cassandra engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Apache Cassandra Architect