lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-11778) Add per-stage RequestHandler metrics
Date Fri, 02 Feb 2018 13:31:00 GMT


ASF subversion and git services commented on SOLR-11778:

Commit ce5932fc373ebfa6718af8f317b36bf33896a59e in lucene-solr's branch refs/heads/master
from [~ab]
[;h=ce5932f ]

SOLR-11778: Docs for per-stage metrics, and the missing "regex" parameter docs.

> Add per-stage RequestHandler metrics
> ------------------------------------
>                 Key: SOLR-11778
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message