Coordination for Solr. Never selected on its own: Solr pulls it in, and it runs on the same machine as Solr.
Solr runs in cloud mode and keeps its configuration in ZooKeeper: the collections, their schemas, the login. ZooKeeper runs as a single node and keeps its data on disk, so a restart loses nothing. It clears out its old snapshots once a day.
Your application never talks to it. Solr finds it at zookeeper:2181. Its
memory is sized from the machine it runs on.
Versions
| Version | Status |
|---|---|
3.9 |
Supported, and the default |
Pin the version, not the build: name 3.9 and the platform matches it to the
current build, so a security rebuild reaches you without anybody editing a
repository.
The version you name is the one your environment runs from the next deploy. This service keeps data, and not every version can read another's — before you change it, read Changing a service's version.
What you can change
Nothing on this one. Everything it takes decides where it connects, what it is, or whether it starts — and an application able to set those could break its own environment in ways nothing here would catch.
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console