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 2026/09/29 19:01:00 UTC

[jira] [Updated] (SOLR-18124) Tracing: Recovery / Replication

     [ https://issues.apache.org/jira/browse/SOLR-18124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley updated SOLR-18124:
--------------------------------
    Summary: Tracing: Recovery / Replication  (was: Tracing: UpdateLog replay deserves a span (per log))

> Tracing: Recovery / Replication
> -------------------------------
>
>                 Key: SOLR-18124
>                 URL: https://issues.apache.org/jira/browse/SOLR-18124
>             Project: Solr
>          Issue Type: Improvement
>          Components: tracing
>            Reporter: David Smiley
>            Priority: Minor
>              Labels: newdev, pull-request-available
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> When recovering/replaying from the updatelog, this deserves a tracing span.  Both overall, and per-log.
> If possible, it'd be nice to include the URP chain as metadata, and some basic per-log stats.



--
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