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

Jan Høydahl commented on SOLR-16532:
------------------------------------

Yes, had the same thread leak locally at first, but after implementing 
"ClosableTracerShim" which closes the OTEL Sdk tracer, it was fine locally. 
Probably something that is slower in Jenkins so it trips.

The BSP thread hanging is probably trying to connect to acollector, but as 
we're just testing init, and not actual tracing, we have not setup any 
collector. So I lowered OTEL_BSP_SCHEDULE_DELAY and OTEL_BSP_EXPORT_TIMEOUT to 
make sure the span exporter shuts down. The threadpool is managed by OTEL 
itself. 

We can avoid the complexity of background thread by selecting e.g. 
OTEL_TRACES_EXPORTER=logging, which will write traces to logfile instead, using 
synchronous SimpleSpanProcessor. Or we could try to increase 
@ThreadLeakLingering to 15s due to the hardcoded 10s timeout during close() 
here: 
[https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/SdkTracerProvider.java#L132-L135]

Wdyt?

> New OpenTelemetry module with OTLP trace exporter
> -------------------------------------------------
>
>                 Key: SOLR-16532
>                 URL: https://issues.apache.org/jira/browse/SOLR-16532
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: tracing
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>             Fix For: 9.2
>
>          Time Spent: 8h 40m
>  Remaining Estimate: 0h
>
> This module can be added alongside the jaegertracer-configurator module.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to