[
https://issues.apache.org/jira/browse/SOLR-16620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756855#comment-17756855
]
Eric Pugh edited comment on SOLR-16620 at 8/21/23 11:32 AM:
------------------------------------------------------------
[~houston]is the description above still accurate? Was going to look at this
one. Also, I *think* at this point, we could write a bats test with ssl and
auth enabled right? At least, for basic Auth?
Also, are you thinking that we have a default? --state=ready or --state=live
or if you don't have --state we give it all back?
was (Author: epugh):
[~houston]is the description above still accurate? Was going to look at this
one. Also, I *think* at this point, we could write a bats test with ssl and
auth enabled right? At least, for basic Auth?
> Solr CLI should be able to do a node healthcheck
> ------------------------------------------------
>
> Key: SOLR-16620
> URL: https://issues.apache.org/jira/browse/SOLR-16620
> Project: Solr
> Issue Type: Improvement
> Components: SolrCLI
> Reporter: Houston Putman
> Priority: Major
>
> This healthcheck only needs to work for the localhost, but obviously support
> a customized port.
> This healthcheck command should also support a healthcheck type, such as
> "ready" or "live". The backend API calls for these types can change over
> time, but "admin/info/health" is a good start for "ready" and
> "admin/info/system" can be the first implementation for "live".
> Future tickets can be spun off to make each implementation better.
> These healthchecks should work with TLS and Auth if either is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
