[
https://issues.apache.org/jira/browse/SOLR-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950362#comment-13950362
]
Otis Gospodnetic commented on SOLR-5749:
----------------------------------------
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.
Re naming - I think good names and consistency is important. Applications get
judged by how things are structured and named, too, not just whether they work
or not or how well they work. :) Not seeing that consistency bugs me, but it
won't break things...
> Implement an Overseer status API
> --------------------------------
>
> Key: SOLR-5749
> URL: https://issues.apache.org/jira/browse/SOLR-5749
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.8, 5.0
>
> Attachments: SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch,
> SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch
>
>
> Right now there is little to no information exposed about the overseer from
> SolrCloud.
> I propose that we have an API for overseer status which can return:
> # Past N commands executed (grouped by command type)
> # Status (queue-size, current overseer leader node)
> # Overseer log
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
