You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Mayya Sharipova (Jira)" <ji...@apache.org> on 2021/06/23 13:50:10 UTC

[jira] [Updated] (SOLR-15452) TracingUpdateProcessor for distributed tracing

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

Mayya Sharipova updated SOLR-15452:
-----------------------------------
    Security:     (was: Public)

> TracingUpdateProcessor for distributed tracing
> ----------------------------------------------
>
>                 Key: SOLR-15452
>                 URL: https://issues.apache.org/jira/browse/SOLR-15452
>             Project: Solr
>          Issue Type: Improvement
>          Components: UpdateRequestProcessors
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>
> Commits, Optimizes, MergeIndexes are heavy operations that are worthy of putting a Distributed Tracing "span" around (or at a minimum, at least a span log).
> I propose to accomplish this using the nice UpdateRequestProcessor abstraction.  Consider that this approach is taken for logging and some other things.  If the active Span is non-existent or a no-op, then there will be no added overhead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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