[
https://issues.apache.org/jira/browse/SOLR-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-16943:
--------------------------------
Description: Instead of injecting tracing at HttpShardHandler &
SolrCmdDistributor, go deeper at InstrumentedHttpListenerFactory, thereby
covering more use-cases. A random example is
org.apache.solr.update.processor.DistributedUpdateProcessor#fetchFullUpdateFromLeader
which currently isn't traced. (was: Adding a client side span is useful to
see bottlenecks in client-server interaction, especially async delivery delays.
Additionally: Instead of injecting tracing at HttpShardHandler &
SolrCmdDistributor, go deeper at InstrumentedHttpListenerFactory, thereby
covering more use-cases. A random example is
org.apache.solr.update.processor.DistributedUpdateProcessor#fetchFullUpdateFromLeader
which currently isn't traced.)
> Add client tracing spans to HTTP interaction; at least for Jetty HttpClient
> ---------------------------------------------------------------------------
>
> Key: SOLR-16943
> URL: https://issues.apache.org/jira/browse/SOLR-16943
> Project: Solr
> Issue Type: Improvement
> Components: tracing
> Reporter: David Smiley
> Priority: Major
> Time Spent: 6h 10m
> Remaining Estimate: 0h
>
> Instead of injecting tracing at HttpShardHandler & SolrCmdDistributor, go
> deeper at InstrumentedHttpListenerFactory, thereby covering more use-cases.
> A random example is
> org.apache.solr.update.processor.DistributedUpdateProcessor#fetchFullUpdateFromLeader
> which currently isn't traced.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
