Skip to content

Commit 0d9a1da

Browse files
jebnixjanhoy
andauthored
Link Solr Operator for learning on Solr in Kubernetes, and better exp… (#1114)
* Remove docker-networking.adoc page * Write a few paragraphs about cloud in the FAQ * Remove bad advice about docker links * Remove info about legacy v5-7 * Add example of compose file for cloud Co-authored-by: Jan Høydahl <[email protected]>
1 parent e7f3a79 commit 0d9a1da

File tree

5 files changed

+47
-329
lines changed

5 files changed

+47
-329
lines changed

dev-docs/running-in-docker.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# Running Solr in Docker
1+
= Running Solr in Docker
22

33
You can run Solr in Docker via the https://hub.docker.com/_/solr[official image].
44
@@ -11,7 +11,7 @@ In order to start Solr in cloud mode, run the following.
1111
`docker run -p 8983:8983 solr solr-fg -c`
1212
1313
For documentation on using the official docker builds, please refer to the https://hub.docker.com/_/solr[DockerHub page].
14-
Up to date documentation for running locally built images of this branch can be found in the xref:_running_solr_in_docker[local reference guide].
14+
Up-to-date documentation for running locally built images of this branch can be found in the xref:_running_solr_in_docker[local reference guide].
1515

1616
There is also a gradle task for building custom Solr images from your local checkout.
1717
These local images are built identically to the official image except for retrieving the Solr artifacts locally instead of from the official release.
@@ -29,5 +29,5 @@ For more info on building an image, run:
2929

3030
`./gradlew helpDocker`
3131

32-
## Additional Information
32+
== Additional Information
3333
You can find additional information in the https://solr.apache.org/guide/solr/latest/deployment-guide/solr-in-docker.html[Solr Ref Guide Docker Page]

solr/solr-ref-guide/modules/deployment-guide/deployment-nav.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,6 @@
2929
** xref:backup-restore.adoc[]
3030
** xref:solr-in-docker.adoc[]
3131
*** xref:docker-faq.adoc[]
32-
*** xref:docker-networking.adoc[]
3332
** xref:solr-on-hdfs.adoc[]
3433
3534
* Scaling Solr

solr/solr-ref-guide/modules/deployment-guide/pages/docker-faq.adoc

Lines changed: 11 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -49,30 +49,17 @@ docker run --rm -p 8983:8983 -v solrData:/mysolrhome solr:9-slim
4949

5050
== Can I run ZooKeeper and Solr clusters under Docker?
5151

52-
At the network level the ZooKeeper nodes need to be able to talk to each other,
53-
and the Solr nodes need to be able to talk to the ZooKeeper nodes and to each other.
54-
At the application level, different nodes need to be able to identify and locate each other.
55-
In ZooKeeper that is done with a configuration file that lists hostnames or IP addresses for each node.
56-
In Solr that is done with a parameter that specifies a host or IP address, which is then stored in ZooKeeper.
57-
58-
In typical clusters, those hostnames/IP addresses are pre-defined and remain static through the lifetime of the cluster.
59-
In Docker, inter-container communication and multi-host networking can be facilitated by https://docs.docker.com/engine/userguide/networking/[Docker Networks].
60-
But, crucially, Docker does not normally guarantee that IP addresses of containers remain static during the lifetime of a container.
61-
In non-networked Docker, the IP address seems to change every time you stop/start.
62-
In a networked Docker, containers can lose their IP address in certain sequences of starting/stopping, unless you take steps to prevent that.
63-
64-
IP changes cause problems:
65-
66-
* If you use hardcoded IP addresses in configuration, and the addresses of your containers change after a stops/start, then your cluster will stop working and may corrupt itself.
67-
* If you use hostnames in configuration, and the addresses of your containers change, then you might run into problems with cached hostname lookups.
68-
* And if you use hostnames there is another problem: the names are not defined until the respective container is running,
69-
So when for example the first ZooKeeper node starts up, it will attempt a hostname lookup for the other nodes, and that will fail.
70-
This is especially a problem for ZooKeeper 3.4.6; future versions are better at recovering.
71-
72-
Docker 1.10 has a new `--ip` configuration option that allows you to specify an IP address for a container.
73-
It also has a `--ip-range` option that allows you to specify the range that other containers get addresses from.
74-
Used together, you can implement static addresses.
75-
See the xref:docker-networking.adoc[] for more information.
52+
Yes. You can simply start your Solr containers in "Cloud mode", pointing
53+
them to a xref:zookeeper-ensemble.adoc[Zookeeper Ensemble].
54+
55+
For local development, using a single zookeeper container is enough.
56+
Please consult the https://hub.docker.com/_/zookeeper[Zookeeper docker image] for details.
57+
58+
For production purposes, we discourage rolling your own Zookeeper orchestration,
59+
as there are many pitfalls. Instead, use a well-supported container orchestrator
60+
with support for Solr and Zookeeper. For Kubernetes, we provide the
61+
https://solr.apache.org/operator/[Solr Operator] sub project.
62+
There are also 3rd party Helm charts available.
7663

7764
== How can I run ZooKeeper and Solr with Docker Compose?
7865

solr/solr-ref-guide/modules/deployment-guide/pages/docker-networking.adoc

Lines changed: 0 additions & 279 deletions
This file was deleted.

0 commit comments

Comments
 (0)