epugh commented on code in PR #4886:
URL: https://github.com/apache/solr/pull/4886#discussion_r3959162424
##########
solr/solr-ref-guide/modules/configuration-guide/pages/implicit-requesthandlers.adoc:
##########
@@ -40,24 +40,8 @@ This handler must have a collection name in the path to the
endpoint.
|`solr/<collection>/admin/file`
|{solr-javadocs}/core/org/apache/solr/handler/admin/ShowFileRequestHandler.html[ShowFileRequestHandler]
|`_ADMIN_FILE`
|===
-Health:: Report the health of the node.
-+
-[cols="3*.",frame=none,grid=cols,options="header"]
-|===
-|API Endpoints |Class & Javadocs |Paramset
-|v1: `solr/admin/info/health`
-
-v2: `api/node/health` |v1:
{solr-javadocs}/core/org/apache/solr/handler/admin/HealthCheckHandler.html[HealthCheckHandler]
-
-v2:
{solr-javadocs}/core/org/apache/solr/handler/admin/api/NodeHealth.html[NodeHealth]
|
-|===
-+
-In SolrCloud mode the handler checks that the node is connected to ZooKeeper
and is listed in live nodes.
-The optional `requireHealthyCores=true` parameter additionally requires that
all local replicas be in an active state, which is useful for rolling-restart
probes.
-+
-In user-managed (leader-follower) mode the handler checks replication lag.
-The optional `maxGenerationLag=<n>` parameter specifies the maximum number of
Lucene commit generations by which a follower is allowed to trail its leader;
the endpoint returns HTTP 503 if any core exceeds this threshold.
-See
xref:deployment-guide:user-managed-index-replication.adoc#monitoring-follower-replication-lag[Monitoring
Follower Replication Lag] for details and examples.
+Health:: Report the health of the node, via the `api/node/health` endpoint
({solr-javadocs}/core/org/apache/solr/handler/admin/api/NodeHealth.html[NodeHealth]).
+See xref:deployment-guide:healthcheck.adoc[] for details, parameters, and
examples.
Review Comment:
yeah, we don't want v1, so why explain it? Maybe it should be listed until
we remove V1? Happy to go whichever way you think...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
