Move routing stuff to one document

vespa-engine · Sep 27, 2023 · 7668fcb · 7668fcb
1 parent 1ffe191
commit 7668fcb
Show file tree

Hide file tree

Showing 11 changed files with 796 additions and 1,091 deletions.
diff --git a/_data/sidebar.yml b/_data/sidebar.yml
@@ -370,8 +370,6 @@ docs:
         url: /en/reference/config-files.html
       - page: mTLS Reference
         url: /en/reference/mtls.html
-      - page: Routingpolicies Reference
-        url: /en/reference/routingpolicies.html
       - page: Internal Configuration File Reference
         url: /en/reference/internal-config-files.html
       - page: Healthchecks Reference

diff --git a/en/document-processing.html b/en/document-processing.html
@@ -92,7 +92,7 @@ <h2 id="deploying-a-document-processor">Deploying a Document Processor</h2>
   For example, the route <code>default/chain.my-chain indexing</code> would route feed operations
   through the chain "my-chain" in the "default" container cluster, and then to the "indexing" hop,
   which resolves to the specified indexing chain for each content cluster the document should be sent to.
-  More details can be found in <a href="indexing.html#document-processing">indexing</a>:
+  More details can be found in <a href="/en/operations-selfhosted/routing.html#document-processing">indexing</a>:
 </p>
 
 

diff --git a/en/indexing.html b/en/indexing.html
diff --git a/en/operations-selfhosted/routing.html b/en/operations-selfhosted/routing.html
diff --git a/en/operations/reindexing.html b/en/operations/reindexing.html
@@ -43,7 +43,7 @@ <h2 id="reindexing-progress">Reindexing progress</h2>
 <p>
   Reindexing is done by a component in each content cluster that
   <a href="../visiting.html">visits</a> all documents of the indicated types,
-  and re-feeds these through the <a href="../indexing.html#chain-indexing">indexing chain</a> of the cluster.
+  and re-feeds these through the <a href="/en/operations-selfhosted/routing.html#chain-indexing">indexing chain</a> of the cluster.
   (Note that only the <a href="../reference/schema-reference.html#document">document fields</a> are re-fed —
   all derived fields, produced by the indexing pipeline, are recomputed.)
   The reindexing process avoids write races with concurrent feed by locking

diff --git a/en/operations/using-kubernetes-with-vespa.html b/en/operations/using-kubernetes-with-vespa.html
@@ -17,7 +17,7 @@
   Use the <a href="https://github.com/vespa-engine/sample-apps/tree/master/examples/operations/multinode-HA/gke">
   multinode-HA</a> sample application as a basis for configuration.
 </p>
-<img src="/assets/img/vespa-overview.svg" src="Vespa overview illustration"
+<img src="/assets/img/vespa-overview.svg" alt="Vespa overview illustration"
      width="825px" height="auto" />
 <ul>
   <li>

diff --git a/en/performance/sizing-feeding.html b/en/performance/sizing-feeding.html
@@ -20,7 +20,7 @@
   and includes both Vespa-internal processing like <a href="../linguistics.html#tokenization">tokenization</a>
   and application custom code in <a href="../document-processing.html">document processing</a>.
   The stateless cluster is primarily CPU bound,
-  read <a href="../indexing.html#multiple-container-clusters">indexing</a>
+  read <a href="/en/operations-selfhosted/routing.html#multiple-container-clusters">indexing</a>
   for how to separate search and write to different container clusters.
   Other than that, make sure the container cluster has enough memory to avoid excessive GC -
   the <a href="container-tuning.html">heap</a> must be big enough.

diff --git a/en/reads-and-writes.html b/en/reads-and-writes.html
@@ -45,7 +45,7 @@
 <li>
   Applications can <a href="documents.html#document-expiry">auto-expire documents</a>.
   This feature also blocks PUTs to documents that are already expired -
-  see <a href="indexing.html#document-selection">indexing</a> and
+  see <a href="/en/operations-selfhosted/routing.html#document-selection">indexing</a> and
   <a href="reference/services-content.html#documents">document selection</a>.
   This is a common problem when feeding test data with timestamps,
   and the writes a silently dropped.
@@ -225,7 +225,7 @@ <h2 id="feed-flow">Feed flow</h2>
 </p>
 <img src="/assets/img/elastic-feed-vespafeeder.svg" width="345" height="auto" alt="Feed with vespafeeder"/>
 <p>
-  <a href="indexing.html">Indexing</a>
+  <a href="/en/operations-selfhosted/routing.html#routing-for-indexing">Indexing</a>
   and/or <a href="document-processing.html">document processing</a>
   is a chain of processors that manipulate documents before they are stored.
   Document processors can be user defined.

diff --git a/en/reference/routingpolicies.html b/en/reference/routingpolicies.html