This is an automated email from the ASF dual-hosted git repository. asf-gitbox-commits pushed a commit to branch branch_10_1 in repository https://gitbox.apache.org/repos/asf/solr.git
commit ddea63328afeebae084bd1eefa028a5ee7014561 Author: Eric Pugh <[email protected]> AuthorDate: Sun Sep 27 18:23:25 2026 -0400 SOLR-18417: Fix broken ref guide link (#4954) (cherry picked from commit b047b21d44cf7ded00c589ed6dd61c1af668c86d) (cherry picked from commit e2ab63d912ee5d547202f1dfd09dade1ad0027d7) --- solr/solr-ref-guide/modules/deployment-guide/pages/healthcheck.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/healthcheck.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/healthcheck.adoc index 7e5bc472214..c4df352688c 100644 --- a/solr/solr-ref-guide/modules/deployment-guide/pages/healthcheck.adoc +++ b/solr/solr-ref-guide/modules/deployment-guide/pages/healthcheck.adoc @@ -53,7 +53,7 @@ It is designed to be cheap enough to poll frequently from a load balancer or an ==== None of these checks touch the index. A node with a collection that has zero documents, or a collection whose query results are wrong, will still report a healthy `200 OK` here. -If you need to confirm a collection actually has data, see <<Collection Data Healthcheck>> below. +If you need to confirm a collection actually has data, see <<Collection Healthcheck>> below. ==== What the endpoint checks -- and how it fails -- depends on whether the node is running in SolrCloud mode or user-managed (leader-follower) mode.
