Hey all, Is Solr's "ping" API still useful for folks today?
"/admin/ping" was initially designed as a healthcheck for individual SolrCore instances. The idea was that it could be checked periodically by an external loadbalancer (that, presumably, was aware not just of Solr nodes but of the topology of cores across the cluster). This made sense in 2012 when /admin/ping was introduced, but I'm not so sure it still does today. AFAICT, over time Solr usage has come to prefer node-level healthchecks, and other APIs have sprung up to meet that need. (e.g. the /admin/info/system and /admin/info/health endpoints commonly used as liveness/readiness probes in Kubernetes environments). Even SolrJ's "load-balancing" client (used by both cloud and "standalone" deployments) relies on node-level checks. And of course the advent and prevalence of SolrCloud have even further reduced the need to track per-core health outside of Solr/ZK. Does /admin/ping still have usecases that can't be met by other APIs? Or should we consider deprecating and removing it in 10.0? Best, Jason --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
