lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Potter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5749) Implement an Overseer status API
Date Tue, 04 Mar 2014 16:05:20 GMT

    [ https://issues.apache.org/jira/browse/SOLR-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919552#comment-13919552
] 

Timothy Potter commented on SOLR-5749:
--------------------------------------

Would it make sense to also include metrics for the overseer (possibly using the codahale
stuff described in SOLR-4735)? These metrics could then support the decision to apply SOLR-5746
(dedicated/higher-end node for overseer). Key metrics I'd be interested in tracking are:

1) metrics about how many messages per second / minute the overseer is processing
2) metrics about how long it takes to process each type of operation (leader, state, etc.)
3) metrics around queue sizes / activity (e.g. workQueue has 1000 messages pending)

> 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
>             Fix For: 5.0
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message