You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2025/07/01 03:02:00 UTC

[jira] [Commented] (SOLR-17799) Revamp segment merge metrics

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

David Smiley commented on SOLR-17799:
-------------------------------------

_Ideally_ we needn't make such a distinction if we can rely on the metrics store or aggregation point before then to make such a distinction.  But I don't have much experience with them, TBH.

> Revamp segment merge metrics
> ----------------------------
>
>                 Key: SOLR-17799
>                 URL: https://issues.apache.org/jira/browse/SOLR-17799
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Kevin Liang
>            Priority: Minor
>
> Based on current [documentation|https://solr.apache.org/guide/solr/latest/deployment-guide/metrics-reporting.html#index-merge-metrics] for segment merge metrics, there are two major groups of metrics emitted (for currently actively running merges and for merges that have completed). The actively running ones are gauges that can go up or down, while the ones for completed are counters/timers.
> To make these metrics more consistent and aggregate-able, propose emitting all metrics for merges as running counters for # of merges, # of segments, and # of documents with a metric for each tracking started/completed (thus active merges can be calculated via the current diff between the two).
> Relates to original feature from https://issues.apache.org/jira/browse/SOLR-9854



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org