MongoDB support

24/7 MongoDB Support for Community Edition

Last reviewed by Tyler Eastridge

AceMQ supports MongoDB 24/7 across Americas, EMEA and APAC on self-managed Community Edition, Enterprise Advanced and Atlas clusters. Calls usually begin with one of three problems: write stalls from WiredTiger cache pressure, replica set elections and lagging secondaries, or a shard key that sends all writes to one shard.

AceMQ provides 24/7 MongoDB support for Community Edition, which has no vendor support of its own, and for Atlas and Enterprise Advanced clusters. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge on a P1, and every P1 ends in a written root-cause analysis. We cover MongoDB 4.2 to 9.0, and patched builds of self-managed Community 4.2 to 6.0 are available through OSSeva after MongoDB's end of life.

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

Planning a build, upgrade or migration instead? See AceMQ MongoDB 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

Problems we fix every week

Replica set and sharded cluster trouble, listed by what the application sees, with the oplog, balancer or connection counters we inspect for each.

Common MongoDB production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Write latency rises in steps while queries look unchangedCheck db.serverStatus().wiredTiger.cache for "tracked dirty bytes in the cache" against the cache size, and eviction counters. When application threads join eviction, latency stops being linear. cacheSizeGB set from the host rather than the container limit is a frequent cause.
The oplog window shrinks to hoursRun rs.printReplicationInfo() and rs.printSecondaryReplicationInfo(). Bulk updates that rewrite whole documents amplify oplog volume, so one slow secondary can trigger a full resync.
A sharded collection will not balanceRun sh.status() and look for jumbo chunks, then db.collection.getShardDistribution(). A monotonically increasing key puts every insert on one shard, and the balancer cannot fix that.
Queries are fast on the primary and slow on secondariesCompare explain("executionStats") on each member and check read preference and maxStalenessSeconds. Index builds that finished on the primary but not on a secondary give exactly this split.
Connections climb until the host runs out of memoryCheck db.serverStatus().connections and the driver pool settings (maxPoolSize, maxIdleTimeMS). Many application instances each holding a default-sized pool multiply into thousands of connections.
An index build or compact hurts production during the dayCheck db.currentOp() for long-running index builds and the commitQuorum. We move the build to a window, or build it rolling across members.
Backups restore but take far longer than the recovery objectiveTime a real restore of a representative copy, then compare it with the objective on paper. Point-in-time recovery needs the oplog window to cover the gap between backup and failure.

Every P1 is followed by a written analysis naming the collection, index or node at fault.

Secondaries lagging or writes stalling? Request a quote and a MongoDB engineer comes back within the hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Community Edition, self-managedEverything operational: incidents, indexes, replica sets, sharding, upgrades, security configurationNothing: MongoDB documents community forums and docs for CommunityDefects needing a change to MongoDB's code
Enterprise Advanced, self-managedOperations beside MongoDB's ticket: incidents, tuning, upgrade rehearsalMongoDB subscription support for the productFeatures that only MongoDB can patch
AtlasSchema, index and query design, sharding choices, driver behaviour, cost reviewMongoDB runs the platform under the Atlas support plan you buyFaults in Atlas's service layer
Percona Server for MongoDB and Amazon DocumentDBOperations and performance; compatibility testing for DocumentDBThe vendor covers its own productDocumentDB features that differ from MongoDB

Support options

Vendor support or independent support for MongoDB?

MongoDB support plans (Atlas)
AceMQ independent support
Community EditionAtlas plans cover Atlas only; MongoDB's page lists docs, FAQ and community forums for the free tier
Community EditionCovered, 24/7
Response goalsBasic: free, chat Monday to Friday, no initial-response target. Developer: first response within 8 hours, 24/7 through the Case Portal. Pro: options from 2 hours, phone added. Enterprise: options from 15 minutes to 2 hours
Response goals24/7, from 15 minutes, by plan
Who answersMongoDB support engineers
Who answersAceMQ senior engineers assigned to your account
Product patchesYes
Product patchesNo vendor patches
PricingPro and Enterprise: set in the Atlas UI or by contacting MongoDB
Pricing$24,000 to $72,000 a year (USD), by SLA, scope and deployment

What's Included

Everything in your MongoDB support contract

Community, Enterprise Advanced and Atlas deployments get the same attention on queries, indexes, shards, upgrades and security patches.

  • 01

    Emergency Incident Response

    Primary down, replica set without a quorum, or a cluster that won't accept writes. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement email.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific index, schema, or configuration change that prevents a repeat. Delivered as standard, not on request.

  • 03

    Query & Index Tuning

    Index design against your real query shapes, compound index prefix ordering, covered queries, and killing the redundant indexes that slow every write. We work from $indexStats and profiler output, not guesses.

  • 04

    Schema & Sharding Review

    Shard key selection, chunk distribution, and the anti-patterns that bite later — unbounded arrays, massive documents, and one-collection-per-tenant designs that break the catalog at scale.

  • 05

    CVE & Patch Advisory

    Alerts for CVEs affecting your exact MongoDB version and driver, with tested upgrade paths. We track the feature-compatibility-version steps that make a major upgrade reversible.

  • 06

    Upgrades & Migrations

    Rolling version upgrades, self-managed to Atlas moves (and back), replica set to sharded cluster conversions, and migrations onto or off MongoDB where the data model genuinely argues for it.

Why AceMQ

What MongoDB teams get from AceMQ

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your replica set layout, your shard key, and your traffic shape — so a P1 call opens with diagnosis instead of twenty minutes of you describing the cluster.

  • No First-Line Triage Layer

    You reach a senior MongoDB engineer directly by phone, email, or Slack. Nobody collects information to pass along, and there is no escalation approval standing between you and the person who can actually fix it.

  • Schema Problems Get Called Schema Problems

    A large share of MongoDB incidents are data model incidents wearing an operations costume. We will tell you when the answer is a shard key change or a bucketed collection rather than more RAM, even when more RAM is the easier sale.

  • Atlas and Self-Managed, Both Properly

    Atlas removes patching and backups. It does not remove index design, shard key mistakes, working-set sizing, or connection pool misconfiguration — which is where most incidents actually live. We support both models with the same depth.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am election storm is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to come online.

  • Full-Stack, Not Just mongod

    We diagnose across the driver, the connection pool, the JVM or Node runtime, storage latency, network policy, and Kubernetes. MongoDB symptoms frequently have causes two layers below the database.

MongoDB deployments we cover

Replica sets and sharded clusters across the major clouds, Kubernetes operators, Percona builds and Atlas projects.

  • MongoDB Atlas (all tiers)
  • MongoDB Enterprise Advanced
  • MongoDB Community 4.2 – 9.0
  • Amazon DocumentDB
  • AWS (EC2, ECS, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Kubernetes & OpenShift
  • Percona Server for MongoDB
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • Hybrid cloud

Version coverage

MongoDB versions we support

MongoDB versions we support
Release lineWhat we do on it
9.024/7 support and new-cluster design
8.024/7 support and upgrade planning to 9.0
7.024/7 support and upgrade to 8.0
6.0 and 5.024/7 support and stepwise upgrade, one major release at a time
4.4 and 4.224/7 support and upgrade planning

MongoDB upgrades go one major release at a time, so a plan for an older cluster lists each hop with its feature compatibility version (FCV) step.

Consulting

MongoDB consulting and professional services

Project work with a written outcome, separate from the support contract. Named deliverables: Deployment health assessment: a written review of replica set design, oplog sizing, index usage, cache behaviour, backup restore time and security configuration, with a ranked fix list. Index and query review: unused and redundant indexes, missing indexes with the query shapes that need them, and explain evidence for each change. Shard key and sharding design: access-pattern profile, candidate key evaluation and a phased migration plan with rollback. Upgrade plan and rehearsal: the hop-by-hop path from your version to 7.0, 8.0 or 9.0, driver compatibility notes and a rehearsal on a restored copy. Backup and recovery design: point-in-time recovery objectives, a timed restore test and a runbook. Is MongoDB still the right store? An honest assessment of workloads that suit PostgreSQL JSONB better, and those that do not.

Escalation Path

Your first hour of a MongoDB outage

On a write stall or a secondary that fell off the oplog, you speak to someone who reads mongod logs daily, not a ticket router.

  1. From 15 min (by plan)first responseEmergencyProduction outage: no primary elected, a shard unavailable, or the cluster refusing connections
  2. 1 hourfirst responseCriticalHeavy degradation: write latency climbing, oplog window too short for a resync, connection counts nearing host limits
  3. 4 hoursfirst responseHighChunk migrations stuck, secondary reads slow, index builds interfering with daytime load
  4. Next Dayfirst responseStandardIndex and schema review, shard key questions, upgrade runbooks, backup restore timing and patch guidance

Your plan sets the clock, so a stalled primary is not queued behind a schema question.

Looking for a named MongoDB specialist who already knows your shard layout? Get a quote or drop us a note.

Contact Us

Pricing

What does AceMQ MongoDB support cost?

MongoDB support is typically $24,000 to $72,000 a year. Cost follows the number of replica sets and shards, the edition and version, whether Atlas is part of the picture, and how quickly you need a response.

Prices are in US dollars (USD). Response targets run from 15 minutes by plan, 24/7, and a quote request is answered within 1 hour. Adding other technologies to one contract earns a multi-technology discount.

Support In Practice

MongoDB cluster problems we have resolved

MongoDB support work from AceMQ. Each card links to the full write-up: the cluster, what AceMQ diagnosed or changed, and the result.

  • Remediation

    MongoDB WiredTiger Cache Eviction Remediation

    Global Payments Processor

    Diagnosing and resolving application stalls caused by a working set that outgrew the WiredTiger cache, pushing the server into continuous eviction pressure.

    MongoDBKubernetesPrometheusLinux
  • Support

    MongoDB Replica Set and Oplog Window Support

    Healthcare Analytics Provider

    Ongoing support for replica sets where a short oplog window was forcing repeated full initial syncs of secondaries during nightly batch loads.

    MongoDBKubernetesTerraformPrometheus
  • Consulting

    MongoDB Sharding Strategy and Shard Key Redesign

    Logistics and Freight Technology Provider

    Redesigning a monotonically increasing shard key that concentrated all inserts on one shard and produced jumbo chunks that would not split.

    MongoDBKubernetesKafkaTerraform
All use cases

Support options

Four tiers of MongoDB support.

AceMQ offers MongoDB support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for clusters your team runs, proactive monitoring that finds oplog, index and shard-balance problems first, managed MongoDB on your own infrastructure, and fully managed MongoDB on AceMQ infrastructure. Atlas, Enterprise Advanced and Community are covered, and self-managed Community 4.2 to 6.0 can be kept patched through OSSeva.

  • Tier 1

    MongoDB 24/7 Support & Incident Management

    Your DBAs run mongod, we back them up

    Best for: Teams that manage their own replica sets and want an expert one call away when replication or latency fails.

  • Tier 2

    MongoDB 24/7 Support with Proactive Monitoring

    Planned reviews of indexes, oplog and shards

    Best for: Teams that want slow queries, short oplog windows and imbalance found in a review instead of during an outage.

  • Tier 3

    Managed MongoDB on Your Infrastructure

    We operate your MongoDB clusters on your hosts

    Best for: Companies that must keep MongoDB on infrastructure they control but want upkeep and patching handled for them.

  • Tier 4

    Fully Managed MongoDB on AceMQ Infrastructure

    AceMQ runs your replica sets for you

    Best for: Product teams that want a dependable document store without building an in-house MongoDB operations practice.

FAQ

MongoDB support questions

Still have questions about MongoDB? Email an Expert

Who provides enterprise support for MongoDB?

MongoDB, through Atlas support plans and an Enterprise Advanced subscription, and independent providers such as AceMQ. Community Edition has no vendor support, so most teams that run it use an independent provider.

Does MongoDB Atlas support cover my slow queries?

Atlas plans cover the platform and give you access to MongoDB engineers at the plan's response goal. Schema, index and query design remain your responsibility, which is where we add a second pair of senior eyes, at any hour.

How do you plan a MongoDB upgrade without downtime?

Upgrade one major release at a time, rehearse on a restored copy with real drivers, check driver compatibility, then upgrade secondaries first, step down the primary and raise the feature compatibility version only after the new binaries are stable. Each hop has a rollback position agreed in advance.

Is MongoDB Community Edition supported?

By MongoDB, no: its support pages describe documentation and community forums. AceMQ supports it 24/7.

How do I stop a secondary falling off the oplog?

A secondary falls off when the oplog window is shorter than its lag. We compare the window with peak write bursts, resize the oplog where needed, find what is slowing the secondary, and resync only as a last step. Raising the window first usually avoids a full initial sync.

Can you fix a bad shard key without downtime?

Often yes, through resharding with checkpoints and a rehearsal on a production-scale copy. We say so up front when a window is unavoidable.

Do you support Amazon DocumentDB?

Yes, for operations and performance, with compatibility testing where behaviour differs from MongoDB.

How fast do you respond to a MongoDB outage?

Response begins within 15 minutes on the fastest plans, at any hour. Example Sev 1: a replica set loses its primary after a network event and elections keep failing. An engineer joins a bridge, reads rs.status() and the mongod logs, and sends a root cause. P2 1 hour, P3 4 hours, P4 next business day.

Can we hire AceMQ for a single MongoDB project?

Yes. Work such as a version upgrade, a shard key review or an index overhaul can be scoped as its own engagement. Many teams begin that way, then choose a yearly agreement for 24/7 incident cover once they see how the same engineers handle a production event.

What affects the cost of MongoDB support?

Annual contracts normally sit between $24,000 and $72,000 (USD). What moves the number: replica sets and shards in scope, Community versus Enterprise Advanced versus Atlas, how many applications depend on the cluster, and the response plan. Send those details and we return a quote inside 1 hour.

Let's talk

Your MongoDB Cluster Shouldn't Fail Quietly at 3am

Tell us your edition, version and cluster layout. We reply with a quote within 1 hour.

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

Production incident right now?Email a MongoDB Architect