[
https://issues.apache.org/jira/browse/SOLR-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5928:
----------------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: SOLR-5128
> Expose Overseer Status via JMX
> ------------------------------
>
> Key: SOLR-5928
> URL: https://issues.apache.org/jira/browse/SOLR-5928
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
>
> As put eloquently by Otis on SOLR-5749:
> {quote}
> bq. It'd probably be hard for someone to monitor it with jmx because the
> mbeans will be published only on the overseer node (which can change from
> time to time).
> I think good monitoring tools won't have a problem with that. But if you
> expose it through a non-standard API, then it's harder for monitoring tools
> to get to this info because now they need to implement a mechanism to, in
> addition to getting data from JMX, also get this other stats from an
> alternative API with a custom response format.... which makes things messy.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
