* Add new Scaling landing page under Operations
Introduces a Scaling section with vertical vs. horizontal scaling
guidance and failover best practices, linking out to detail pages.
* Add new Vertical Scaling page
Dedicated how-to guidance for resizing existing nodes: when to scale
vertically, RAM sizing formulas, and Cloud/self-hosted resize steps.
* Add new Horizontal Scaling and Resilience page
Covers Raft consensus, the replication model, consistency guarantees,
Multi-AZ, and the resilience terminology used elsewhere in the docs.
* Move Distributed Deployment under Scaling and update all incoming links
Moves distributed_deployment.md into the new scaling/ section, trims
its Raft/Replication/Consistency intros into cross-links to the new
Horizontal Scaling and Resilience page, adds Multi-AZ and single-replica
cross-link callouts in the Cloud docs, rewrites all internal references
across ~30 files to the new canonical path instead of relying on
aliases, and applies Title Case to Distributed Deployment's headers.
* Split Resilience out of Horizontal Scaling and Resilience
Adds a dedicated Resilience page covering fault tolerance, Multi-AZ,
resilience terminology, and failover best practices (moved from the
Scaling landing page). Horizontal Scaling is retitled and scoped to
the underlying mechanics: Raft consensus, replication, and consistency.
* Reorganize Horizontal Scaling's structure
Moves "How Many Qdrant Nodes Should I Run?" from Distributed Deployment
into Horizontal Scaling, adds a conceptual Sharding section, and
reorders Sharding/Replication/Raft Consensus/Consistency. Moves the
remaining conceptual content out of Distributed Deployment: Temporary
Node Failure to Resilience, Error Handling folded into Replication,
sharding heuristics folded into Sharding, and the Consensus
Checkpointing explanation folded into Raft Consensus.
* Rename Scaling section to Scaling & Resilience
Renames the section and restructures the landing page: the vertical-
vs-horizontal decision is now purely about scaling, with a dedicated
Resilience section covering fault tolerance through sharding and
multi-node deployments.
* Polish Vertical Scaling and Resilience page content
Reframes Vertical Scaling's "What Not to Do" as positive "Best
Practices". Reworks Resilience's structure: moves the uptime/data-
integrity terminology into the intro as three distinct aspects of
resilience, and renames "How Resilience Works" to "Setting Up a
Resilient Qdrant Cluster".
* Add diagrams illustrating sharding and replication
Adds cluster diagrams to the Sharding and Replication sections on
Horizontal Scaling to make the shard/replica layout easier to follow.
* Add new Node Failure Recovery page
Extracts the node failure recovery scenarios out of Distributed
Deployment into their own page, with each bolded sub-header converted
to a proper heading, and links updated across Resilience and the
Scaling landing page.
* Add new Consistency Guarantees page
Extracts write consistency factor, read consistency, and write
ordering out of Distributed Deployment into their own page, positioned
after Distributed Deployment.
* Add new "Deploy Behind a Load Balancer" section
Explains why a load balancer is needed in front of a multi-node
Qdrant cluster: avoiding a single point of failure at the entry point
and making sure replicas on every node actually serve reads.
* Add new "Rebalancing" section
Documents how Qdrant Cloud automatically rebalances shards across
nodes, as its own subsection under Sharding.
* Rewrite Multi-AZ vs. Replication Factor as Multi-AZ Deployments
Defines an availability zone on first use, explains why multi-AZ
deployments guard against a zone going down, clarifies that Qdrant
Cloud is zone-aware once enabled, and that self-hosted deployments
need to place and move replicas across zones manually.
* Restructure node-count guidance into One/Two/Three-or-more Node subsections
Splits "How Many Qdrant Nodes Should I Run?" into three subsections
and drops the "balanced" framing for two nodes: it states plainly
that two nodes give more capacity without true high availability.
* Add new "Which Configuration Is Right for You?" section
Summarizes the one/two/three-or-more node tradeoffs in one place
right after the detailed breakdown.
* Add explicit _redirects entry for legacy distributed_deployment URL
Closes the redirect chain: the existing /guides/ and /operations/
legacy rules both terminate at /documentation/distributed_deployment/,
which previously had no explicit _redirects entry and only resolved
via the Hugo alias meta-refresh page.
* Fix all incoming links to Distributed Deployment and pages under Scaling
Repoints two same-page anchors in distributed_deployment.md that broke
when Write Ordering moved to Consistency Guarantees, and one link in
cloud/create-cluster.md that broke when a Resilience heading was
reworded.
* Update time-based sharding diagram and restructure section
* Fix a couple of broken links
* Move 'Consensus Checkpointing' to 'Node Failure Recovery' page
* initial commit; fixed anchor links on internal docs pages
* add back in absolute paths for links in code comments
* fix: update linkchecker include filter to match server port 1314
PR #1629 changed the Hugo server to port 1314 but forgot to update
the --include filter, which still matched port 1313. This caused all
links to be excluded, making the checker a no-op (0 checked, 82277 excluded).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Fix url rewrite regex so images are not impacted
* Fix links from non-documentation pages
* Fix broken links
* more broken links
* more broken links
* broken link
* Add srcset width descriptor to .lycheeignore
* Ignore URLs that contain a % character
* Anchor regex so it matches the entire URL
---------
Co-authored-by: kanungle <neil.kanungo@gmail.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
* use relative links instead of absolute
* add trailing slashes to avoid 301 redirect
* add trailing slashes to avoid 301 redirect
* make link checker unhappy with local redirects
* test if ci fails (should fail)
* rollback: test if ci fails (should fail)
chadha