This is an automated email from the ASF dual-hosted git repository.
epugh pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/branch_9x by this push:
new 9f0b784c074 Update outdated link in docker-networking.adoc (#2164)
9f0b784c074 is described below
commit 9f0b784c0741cccd3c07689af6cb9ee38f7a3d21
Author: Zauberfisch <[email protected]>
AuthorDate: Wed Dec 20 15:10:29 2023 +0100
Update outdated link in docker-networking.adoc (#2164)
---
.../modules/deployment-guide/pages/docker-networking.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/solr/solr-ref-guide/modules/deployment-guide/pages/docker-networking.adoc
b/solr/solr-ref-guide/modules/deployment-guide/pages/docker-networking.adoc
index 66b1b75446e..32f6aa14ce2 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/docker-networking.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/docker-networking.adoc
@@ -16,7 +16,7 @@
// specific language governing permissions and limitations
// under the License.
-_Note: this article dates from Jan 2016. While this approach would still work,
in Jan 2019 this would typically done with Docker cluster and orchestration
tools like Kubernetes. See for example
https://lucidworks.com/2019/02/07/running-solr-on-kubernetes-part-1/[this blog
post]._
+_Note: this article dates from Jan 2016. While this approach would still work,
in Jan 2019 this would typically done with Docker cluster and orchestration
tools like Kubernetes. See for example
https://lucidworks.com/post/running-solr-on-kubernetes-part-1/[this blog post]._
In this example I'll create a cluster with 3 ZooKeeper nodes and 3 Solr nodes,
distributed over 3 machines (trinity10, trinity20, trinity30).
I'll use an overlay network, specify fixed IP addresses when creating
containers, and I'll pass in explicit `/etc/hosts` entries to make sure they
are available even when nodes are down.
