[
https://issues.apache.org/jira/browse/SOLR-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950274#comment-13950274
]
Otis Gospodnetic commented on SOLR-5749:
----------------------------------------
Could this be exposed via JMX, like the rest of the stats?
Could we improve naming a bit?
e.g.
+ lst.add("15minRateReqsPerMinute", timer.getFifteenMinuteRate());
+ lst.add("avgTimePerRequest", timer.getMean());
+ lst.add("medianRequestTime", snapshot.getMedian());
+ lst.add("75thPcRequestTime", snapshot.get75thPercentile());
Note:
* Reqs vs. spelled our Request
* Non-standard "Pc". I think people most often use "Pctl"
> 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]
