Apache Solr support

Solr Support for SolrCloud, ZooKeeper and Standalone Clusters

Last reviewed by Tyler Eastridge

AceMQ provides 24/7 Apache Solr support for SolrCloud with ZooKeeper, standalone and leader-follower clusters on Solr 8, 9 and 10. Most calls start with one of three problems: replicas stuck in recovery after a restart, long garbage-collection pauses that drop nodes, or indexing that falls behind. Apache Solr has no vendor SLA, so we are the escalation path.

AceMQ provides 24/7 Apache Solr support for SolrCloud and user-managed clusters: an AceMQ engineer and a partner Solr specialist on a live bridge for a P1 (response targets from 15 minutes, by plan), a written root-cause analysis after each one, and upgrade planning against the Apache project's version status. Apache Solr is community software with no vendor SLA, so AceMQ is the escalation path your team does not otherwise have. AceMQ does not ship its own Solr builds.

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

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

Solr problems we fix every week, and what an engineer checks first

Recovering replicas, nodes dropped by ZooKeeper, commit storms and slow queries: the API call, log or config file an engineer opens first for each.

Common Apache Solr production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Replicas show down or recovering after a restartCollections API CLUSTERSTATUS for the state of each replica, then the leader election log lines and whether the node came up with a different solr.host or IPFix node identity, wait out or tune leaderVoteWait, then force a leader only as a last step
Node falls out of the cluster after a long pauseGC log for full or mixed pauses against the ZooKeeper session timeout. A pause longer than the session timeout expires the session and drops the nodeResize the heap and heap-hungry caches, tune the collector, then review the timeout
Indexing stalls and logs say maxWarmingSearchers exceededCommit settings: autoCommit (hard) and autoSoftCommit in solrconfig.xml. Clients calling commit on every batch is the usual causeRemove explicit commits, set openSearcher=false on hard commits, lengthen the soft commit interval
Queries slow down after a reindex or upgradedebug=timing on a slow query, then filter cache and query result cache hit ratios from the Metrics API (/admin/metrics) and segment count per shardWarm caches, fix a missing docValues field, or adjust merge policy. We avoid optimize as a reflex
Deep paging makes an export slower with every pageThe request uses large start offsets across shardsSwitch to cursorMark, or /export for sorted bulk reads
ZooKeeper Session expired and an overseer queue that never drainsZnode size and count under /overseer/queue, ensemble health and latency, and the client timeoutClear a stuck queue safely, repair the ensemble, then reduce collection-API churn
Too many open files or an OS kill under loadulimit -n, the segment file count per core and whether the OOM killer ran (dmesg)Raise limits, merge segments sensibly, and reserve memory for the OS page cache

A P1 ends with a written root cause naming the node, setting or query pattern at fault and the change that closes it.

Collection down or replicas stuck in recovery? Send a quote request and a Solr engineer replies inside the hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWhat the project or platform coversExcluded
SolrCloud with an external ZooKeeper ensemble24/7 incident response, RCA on P1s, replica and shard review, ZooKeeper health, rolling upgradesThe Apache project ships the code and releases; it has no support commitmentPatches to Solr itself: we report defects and apply fixes the project releases
User-managed clusters (standalone, leader-follower)Replication lag, failover runbooks, index and query tuningAs aboveCustom forks
Solr on KubernetesPod and storage behaviour as it affects Solr: heap and page cache sizing, persistent volumes, restart orderingThe Kubernetes distribution vendor supports the platformOperator code you do not maintain
Self-managed on VMs, bare metal, AWS, Azure or Google CloudThe Solr and ZooKeeper layerThe cloud provider runs the platformProvider faults
SolrJ and HTTP clientsClient behaviour: CloudSolrClient retries, timeouts and routingNot applicableApplication code is reviewed, not rewritten

Support options

Who provides enterprise support for Solr? The Apache project compared with independent support

Apache Solr is community software: the Apache project publishes releases, and there is no vendor in the loop with a contract and a pager. Enterprise support therefore comes from your own team or from an independent provider. The Apache downloads page notes that community support for older releases may be hard to find (solr.apache.org/downloads.html, read 17 Nov 2026).

Apache Solr project
AceMQ independent support
What it providesSource, releases and community channels
What it providesEngineers on call for your clusters
Response commitmentNone
Response commitmentResponse targets from 15 minutes, by plan
HoursVolunteer and best effort
Hours24/7 across Americas, EMEA and APAC
Root cause analysisNot offered
Root cause analysisWritten RCA on every P1
PriceFree software
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment
FixesReleased by the project when it chooses
FixesWe diagnose, work the fix, and raise defects upstream

Other companies sell Solr-based platforms and support. A platform contract and an independent contract answer different needs: one is a product, the other is engineers for the open-source build you run.

What's Included

Everything in your Apache Solr support contract

SolrCloud collections, shards, replicas and the ZooKeeper ensemble behind them are covered together, along with solrconfig.xml and query tuning.

  • 01

    Emergency Incident Response

    Collection down, replicas not recovering, indexing stopped or a node out of memory. With response targets from 15 minutes, by plan, an AceMQ engineer and a partner Solr specialist join a live bridge, 24/7, to diagnose, not to acknowledge a ticket.

  • 02

    Root Cause Analysis

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

  • 03

    Version and Upgrade Planning

    Where each of your clusters sits against the Apache project's status, and the path to the current line, rehearsed on a copy. The detailed upgrade and migration work is on the Solr consulting page.

  • 04

    Replica, Shard and ZooKeeper Review

    Replica types matched to load, shard counts, backup and restore tested against your recovery target, and ZooKeeper quorum failure runbooks written for your ensemble.

  • 05

    Query and Index Performance

    The slowest recurring queries, cache and commit settings, and the facets and sorts that drive heap use, traced with debug output and metrics rather than guessed at.

  • 06

    Security and Configuration Hygiene

    Authentication, authorization and TLS review, and the defaults that changed in Solr 10, such as JWT blockUnknown now defaulting to true and basic-auth passwords no longer allowed to equal the username.

Why AceMQ

Why search teams call AceMQ for Solr

  • Engineers Who Know Your Environment

    Tickets go to senior engineers briefed on your collections, replica layout and ZooKeeper ensemble, so a P1 call starts with a hypothesis rather than an interview. The proposal states who does the work.

  • No Help-Desk Layer

    You reach a senior engineer directly by phone, email or Slack. No queue collecting details to relay, and no approval between you and someone who can read a Solr log and act.

  • Honest About What We Cannot Patch

    AceMQ does not ship Solr builds. Fixes come from Apache releases, and the project says it will not update end-of-life versions. For a cluster on one, we keep it running, show what is exposed and plan the move.

  • Diagnostics Before Changes

    Debug output, metrics and logs first, then a change with a rollback point. No setting is changed to see what happens in production.

  • Cover Across Time Zones

    AceMQ staffs 24/7 across the Americas, EMEA and APAC, so your 3am alert reaches someone in working hours.

  • One Contract Across Your Search Stack

    Solr rarely runs alone. One AceMQ contract and SLA can also cover Elasticsearch, OpenSearch, Kafka and the databases beside it, with multi-technology discounts.

Solr deployments we cover

SolrCloud on VMs or Kubernetes, user-managed clusters, standalone cores, and ZooKeeper ensembles shared with other services.

  • Apache Solr 8.x, 9.x and 10.x
  • SolrCloud with ZooKeeper
  • User-managed (standalone and leader-follower) clusters
  • SolrJ and HTTP clients, including CloudSolrClient
  • Virtual machines
  • On-premises servers
  • Kubernetes
  • AWS, Azure and Google Cloud instances you run
  • Hybrid estates

Version coverage

Versions we support

Versions we support
Solr lineApache project releasesAceMQ coverage
10.x (10.1.0 is the latest release)Current major version, receives feature releases; needs Java 21 or higher24/7 support
9.11Last release of the 9.x series; may get critical fix releases24/7 support
9.10 and older 9.xNo further Apache releases24/7 support, with an upgrade plan
8.xNo further Apache releases24/7 support, with an upgrade plan
7 and olderNo further Apache releasesScoped case by case

Source: Apache Solr downloads page, solr.apache.org/downloads.html, read 17 Nov 2026. Java 21 requirement for Solr 10 from the Solr Reference Guide, as read by the page author on 31 Oct 2026. The downloads page prints no release dates for these lines, so none are given.

In practice

What a Solr health check looks at before an incident

A fixed-scope review ranks risks before they become P1s. We read the cluster layout (shards, replicas, leaders per node), JVM heap and GC logs, ZooKeeper ensemble size and latency, commit and merge settings, cache hit ratios, the slowest queries from logs, disk headroom and the backup path. The output is a ranked list with one change per item. Ask for it with a support contract or alone.

Who stands behind Solr

What support means for community software

Apache Solr has no vendor in the loop. A page that blurs that sends buyers into the wrong decision, so this one is plain about who does what.

  • What AceMQ provides

    Engineers who run, troubleshoot and upgrade Solr, on-call response, root-cause analysis, version planning and performance diagnosis, under one AceMQ contract and SLA.

  • What stays with the Apache project

    The releases. Fixes and security updates come from Apache Solr, and AceMQ does not fork or rebuild it. Bugs that need a code fix go to the project.

  • If you are on an end-of-life version

    The project lists every release below 9.11 as end of life and does not update them. We map what is exposed and what controls surround it, and you decide with the facts.

  • If you are planning the move

    Upgrades to Solr 10 and migrations to Elasticsearch or OpenSearch are consulting work, scoped and quoted on the Solr consulting page, with support in place meanwhile.

Escalation Path

Your first hour of an Apache Solr outage

Apache Solr has no vendor SLA, so the person on the line is your escalation path and starts from CLUSTERSTATUS and the GC log.

  1. From 15 min (by plan)first responseEmergencyProduction down: a collection offline, replicas unable to recover, indexing stopped, or nodes killed by out-of-memory
  2. 1 hourfirst responseCriticalSevere impact: nodes dropped after GC pauses beyond the ZooKeeper session timeout, an overseer queue that never drains, writes blocked by maxWarmingSearchers
  3. 4 hoursfirst responseHighQueries slower after a reindex or upgrade, deep-paging exports degrading page by page, too many open files under load
  4. Next Dayfirst responseStandardQuestions on autoCommit and autoSoftCommit, cache sizing, shard layout, rolling upgrades and ZooKeeper ensemble size

A collection that stopped taking writes and a question about cache sizing are on different clocks, set by your plan.

Need a specialist who already knows your shards and ZooKeeper setup? Request a quote or message us.

Contact Us

Pricing

What does AceMQ Apache Solr support cost?

Solr support from AceMQ commonly costs $24,000 to $72,000 a year. The price follows your Solr version, the number of clusters and shards, how ZooKeeper is set up and the response plan.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests get an answer within 1 hour. Covering Elasticsearch or OpenSearch under the same contract earns a multi-technology discount.

Typical engagements

Solr incidents we have worked through

Solr incidents where a long GC pause, a commit setting or a deep-paging export turned out to be the real fault.

  • Support

    SolrCloud Replica Recovery and Leader Election Support

    Content Publisher

    A typical emergency engagement: a SolrCloud shard that stopped accepting updates after a node loss, diagnosed from cluster state, replica types and ZooKeeper, with a written root-cause analysis.

    Apache SolrSolrCloudZooKeeperKubernetes
  • Consulting

    Solr 8 to Solr 10 Upgrade Planning

    Software Platform Team

    A typical engagement for a team running Solr 8 in production: a written upgrade path to Solr 10 that names every intermediate version, every reindex and every removed feature, rehearsed on a copy first.

    Apache SolrSolrCloudZooKeeperJava
All use cases

Support options

Four tiers of Apache Solr support.

AceMQ offers Apache Solr support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and emergency response for clusters your team runs, proactive reviews that find replica, ZooKeeper and version problems first, managed Solr on your own infrastructure, and managed Solr on AceMQ infrastructure. Solr 8.x, 9.x and 10.x are covered by AceMQ engineers working with partner Solr specialists. Fixes still come from Apache Solr releases.

  • Tier 1

    Apache Solr 24/7 Support & Incident Management

    Your team runs the clusters, we take escalations

    Best for: Search engineering teams who operate SolrCloud and need an expert for replica recovery, GC pauses and slow queries.

  • Tier 2

    Apache Solr 24/7 Support with Proactive Monitoring

    Planned reviews of shards, commits and ZooKeeper

    Best for: Teams with growing indexes who want commit settings, caches and session timeouts checked before a node drops under load.

  • Tier 3

    Managed Apache Solr on Your Infrastructure

    We operate Solr and ZooKeeper in your environment

    Best for: Organizations keeping their clusters in-house that want routine operation, rolling upgrades and monitoring done by specialists.

  • Tier 4

    Fully Managed Apache Solr on AceMQ Infrastructure

    We run your collections and ZooKeeper for you

    Best for: Teams that need dependable search without staffing for shard management, ZooKeeper care and upgrades.

FAQ

Apache Solr support questions

Still have questions about Apache Solr? Email an Expert

Who provides enterprise support for Solr?

For the open-source build, no vendor does: Apache publishes releases and the community answers questions. AceMQ adds 24/7 support with response from 15 minutes by plan, from engineers who run SolrCloud and ZooKeeper.

Is there commercial support for Apache Solr?

Yes, from independent providers such as AceMQ. It covers incidents, RCA, tuning and upgrade planning for the Solr you run.

Why does my SolrCloud replica stay in recovery?

Usually node identity, a long GC pause, or leader election waiting. See the first row of the problem table.

What does 24/7 Solr support include?

Response from 15 minutes on the top plans, any hour. In a Sev 1 where replicas will not leave recovery after a restart, an engineer checks CLUSTERSTATUS, node identity and GC logs, then writes the root cause. P2 1 hour, P3 4 hours, P4 next business day.

Can you tune Solr query performance?

Yes. We start with debug=timing, cache ratios and segment counts, and make one change at a time.

Which Solr versions do you support?

Solr 8, 9 and 10, with upgrade plans for lines the Apache project no longer releases.

What is the difference between support and managed Solr?

Support: your team runs the clusters and escalates to us. Managed: AceMQ also does the operational work on a schedule.

Can you help us upgrade Solr?

Yes. See /solr/ for upgrade and migration engagements; support covers the plan and the rolling-upgrade runbook.

Can we engage AceMQ for a single Solr task?

Yes. A recovery after an outage, a query performance review, a rolling-upgrade plan or a ZooKeeper review can each be a scoped job. Many customers then move to annual 24/7 cover with the same engineers who did the first piece of work.

What sets the cost of a Solr support agreement?

Most contracts are $24,000 to $72,000 a year (USD). We price by Solr version, number of clusters, collections and shards, the ZooKeeper layout, and the response plan you choose. Send us a short description of the cluster and a quote comes back within 1 hour.

Let's talk

Replicas down tonight, or a search upgrade coming?

Send the Solr version, the number of shards and your ZooKeeper layout. We reply to quote requests within 1 hour.

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

Production incident right now?Email an Apache Solr Architect