[
https://issues.apache.org/jira/browse/SOLR-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774706#comment-17774706
]
ASF subversion and git services commented on SOLR-16943:
--------------------------------------------------------
Commit 4e4c42c3303fe574466dad7d0408a75b7bcf4f1d in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4e4c42c3303 ]
SOLR-16943: Tracing: more thoroughly instrument Solr-to-Solr communication
(#1856)
* Move Jetty HttpClient tracing down into InstrumentedHttpListenerFactory from
other places, thus covering more scenarios.
* Add Apache HttpClient tracing via InstrumentedHttpRequestExecutor.
* None of this affects SolrJ because these "Instrumented" things are only in
solr-core.
* Reinstate Solr ExecutorService instrumentation, i.e. propagation to other
threads in Solr. That was in 9x and briefly was torn out in main.
Co-authored-by: Alex Deparvu <[email protected]>
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Components: tracing
> Reporter: David Smiley
> Priority: Major
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
