What runs on ZooKeeper / solr
Does Apache Solr use ZooKeeper?
Required for SolrCloudYes. SolrCloud keeps its cluster state, collection configuration and leader information in ZooKeeper, and that is still true in Solr 10, released in March 2026. Solr can start an embedded ZooKeeper, but the reference guide says to use an external ensemble in production because the embedded one provides no failover.
Trusted globally by enterprises





What Apache Solr uses ZooKeeper for
- Cluster state: live nodes, collections, shards and replicas.
- Configsets: solrconfig.xml and schema files are uploaded to and read from ZooKeeper.
- Shard leader election and overseer election.
- Security configuration (security.json) for the cluster.
Which ZooKeeper version ships with Apache Solr
From the dependency version files at each release tag. Solr 10 routes all ZooKeeper access through Apache Curator.
| Release | ZooKeeper | ZooKeeper line status | Open ZooKeeper CVEs |
|---|---|---|---|
| Solr 8.0.0 | 3.4.13 | End of life since 1 June 2020Bundles log4j 1.2.17 | 2 (CVE-2019-0201, CVE-2023-44981)2026 advisories not assessed for this line |
| Solr 8.2.0 to 8.5.2 | 3.5.5 | End of life since 1 June 2022Bundles log4j 1.2.17 | 1 (CVE-2023-44981)2026 advisories not assessed for this line |
| Solr 8.6.0 to 8.6.3 | 3.5.7 | End of life since 1 June 2022Bundles log4j 1.2.17 | 1 (CVE-2023-44981)2026 advisories not assessed for this line |
| Solr 8.11.4 (last Solr 8) | 3.6.2 | End of life since 30 December 2022Bundles log4j 1.2.17 | 2 (CVE-2023-44981, CVE-2024-23944)2026 advisories not assessed for this line |
| Solr 9.0.0 | 3.7.0 | End of life since 2 February 2024Bundles log4j 1.2.17 | 2 (CVE-2023-44981, CVE-2024-23944)2026 advisories not assessed for this line |
| Solr 9.10.1 (last Solr 9) | 3.9.4 | Supported (latest 3.9.7) | 7 (CVE-2026-24281, CVE-2026-24308, CVE-2026-59739, CVE-2026-59969, CVE-2026-79993, CVE-2026-84439, CVE-2026-84501) |
| Solr 10.0.0 | 3.9.4 | Supported (latest 3.9.7) | 7 (CVE-2026-24281, CVE-2026-24308, CVE-2026-59739, CVE-2026-59969, CVE-2026-79993, CVE-2026-84439, CVE-2026-84501) |
CVE counts are ZooKeeper's own advisories matched against the upstream version. The Apache ZooKeeper project does not assess end-of-life lines against new advisories, so "not assessed" means unknown, not safe.
What ZooKeeper 3.4.13 is exposed to
CVE-2019-0201 · CVSS 5.9 · fixed in 3.4.14, 3.5.5
getACL() performs no permission check and exposes unsalted digest authentication hashes.
CVE-2023-44981 · CVSS 9.1 · fixed in 3.7.2, 3.8.3, 3.9.1
SASL quorum peer authentication bypass, giving full read-write access to the data tree. Applies when quorum.auth.enableSasl=true.
Find the ZooKeeper Solr is using
# ZooKeeper client jar in the Solr install ls server/solr-webapp/webapp/WEB-INF/lib/ | grep -E '^zookeeper-[0-9]' # The ensemble Solr points at grep -E '^ZK_HOST' bin/solr.in.sh echo srvr | nc zk1.internal 2181 | head -1
Can Apache Solr run without ZooKeeper?
Not in SolrCloud mode. Standalone (user-managed) Solr runs without ZooKeeper but gives up distributed indexing and automatic failover. There is no plan in Solr's issue tracker to remove ZooKeeper.
Solr 8 reached end of life on 25 October 2024. Solr 9.11.0, released 4 October 2026, is the last 9.x release. Solr 10 is the current stable line.
Your options
Upgrade Solr
Solr 8 to 9 or 10 is a real migration, with reindexing where schemas change. It also moves you to a supported ZooKeeper client.
Keep Solr 8, patched
OSSeva patches Solr 7 and 8 and the ZooKeeper ensemble behind them, so a search cluster that cannot be reindexed this quarter stays within audit.
Most teams buy this at the product level: keep the Apache Solr estate supported, including the ZooKeeper under it. See Apache Solr extended support.
ZooKeeper 3.5 custom support for SolrCloud 8.x
Which Solr releases bundle ZooKeeper 3.5? Solr 8.2 through 8.6 ship ZooKeeper 3.5.5 or 3.5.7. Solr 8.7 and later 8.x releases moved to 3.6.2, and Solr 9 to 3.7.0 and newer.
ZooKeeper 3.5 reached end of life on 1 June 2022, and 3.5.10 was its last release, so the Apache project issues no more fixes for it. OSSeva's standard ZooKeeper coverage starts at 3.6. ZooKeeper 3.5 is offered as custom support, scoped per engagement.
Custom support covers CVE backports into 3.5.x builds made from the upstream source, and SBOM and VEX evidence for each build. A scanner finding or an auditor's question then gets a written answer for your configuration: fixed, not present, or not reachable.
SolrCloud keeps cluster state and configsets in ZooKeeper, and the ensemble is a separate install from Solr's own client jar, so it can be on 3.5 even where the Solr nodes are newer. We scope the ensemble and the Solr line together.
Send us the versions you run and we scope it with you. Contact us for a quote.
Releases that bundle ZooKeeper 3.5.x
| Release | Bundled ZooKeeper |
|---|---|
| Solr 8.2.0 to 8.5.2 | 3.5.5 |
| Solr 8.6.0 to 8.6.3 | 3.5.7 |
Source: lucene/ivy-versions.properties at each lucene-solr release tag (github.com/apache/lucene-solr), checked 15 October 2026.
Does Solr need ZooKeeper?
SolrCloud does, in every version including Solr 10. Only standalone, non-cloud Solr runs without it.
Can I use the embedded ZooKeeper that ships with Solr?
For development. The Solr reference guide recommends an external ensemble in production, because the embedded ZooKeeper does not provide failover.
Which ZooKeeper does Solr 8.11 use?
Solr 8.11.4 bundles ZooKeeper 3.6.2. The 3.6 line reached end of life on 30 December 2022 and has no fix for CVE-2023-44981 or CVE-2024-23944.
Get a quote
Keep Apache Solr and the ZooKeeper under it supported.
Send us your versions; we reply with coverage, exposure and a plan within five working days.
Prefer to talk or read more first?