[
https://issues.apache.org/jira/browse/SOLR-11778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350320#comment-16350320
]
ASF subversion and git services commented on SOLR-11778:
--------------------------------------------------------
Commit 32ca792582b49ac509c4d346281a8ed9b9d556b1 in lucene-solr's branch
refs/heads/branch_7x from [~ab]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=32ca792 ]
SOLR-11778 Add per-stage RequestHandler metrics.
> Add per-stage RequestHandler metrics
> ------------------------------------
>
> Key: SOLR-11778
> URL: https://issues.apache.org/jira/browse/SOLR-11778
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-11778.patch
>
>
> Currently {{RequestHandlerBase}} defines several metrics for keeping track of
> general-purpose requests. These metrics are also used in {{SearchHandler}}.
> However, query processing in SolrCloud consists of several (varying) stages,
> and each of these stages may result in additional shard requests. These
> details are not captured by the metrics, because they treat all requests the
> same way.
> In some applications it's important to know how many requests are user
> requests, and how many of them are generated internally by SolrCloud - for
> example, when diagnosing uneven distribution of requests across shards, or
> when autoscaling framework wants to detect "hot replicas". If we split the
> metrics at least into distributed vs. non-distributed requests then the
> numbers become more meaningful and representative of the global load vs.
> local load.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
