[
https://issues.apache.org/jira/browse/SOLR-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950348#comment-13950348
]
Shalin Shekhar Mangar commented on SOLR-5749:
---------------------------------------------
Thanks for reviewing Otis.
bq. Could this be exposed via JMX, like the rest of the stats?
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).
The naming is actually copied over from the RequestHandlerStats.getStatistics,
except that we track requests per minute instead of per second. I thought we
could keep them same in both places for consistency. Would you still prefer to
change?
> 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]
