[
https://issues.apache.org/jira/browse/SOLR-11126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733966#comment-16733966
]
Shalin Shekhar Mangar commented on SOLR-11126:
----------------------------------------------
This is interesting. The system, thread, logging, properties and now health are
registered with the InfoHandler at {{/info/}} path. This InfoHandler is
registered by default in the CoreContainer and there seems to be no way to skip
it. However, the implicit plugins json again defines each of these sub-handlers
directly under the {{/admin/}} path. So each of these handlers are accessibly
through two paths. Also, because the useParams defined in the Implicit plugins
is for {{/admin/xyz}} handler, the paramset won't be applied if the same
handler is accessed using the {{/admin/info/xyz}} path.
[~noble.paul] - do you know why it is done this way? we may need another issue
to clean this up in 8.0
> Node-level health check handler
> -------------------------------
>
> Key: SOLR-11126
> URL: https://issues.apache.org/jira/browse/SOLR-11126
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Anshum Gupta
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (8.0)
>
> Attachments: SOLR-11126-v2.patch, SOLR-11126.patch, SOLR-11126.patch,
> SOLR-11126.patch, SOLR-11126.patch
>
>
> Solr used to have the PING handler at core level, but with SolrCloud, we are
> missing a node level health check handler. It would be good to have. The API
> would look like:
> * solr/admin/health (v1 API)
> * solr/node/health (v2 API)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
