-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[extensions/headerssetter] fatal error: concurrent map writes - collector crashes when multiple exporters uses headers_setter #31289
Comments
Log output part 1
|
Log output part 2
|
Pinging code owners for extension/headerssetter: @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I think I know why this is happening. A request comes in to receiver A. The data (and the request context) flows down the pipeline to exporter X and exporter Y. Both extensions independently access the context in their own threads here. Since 2 threads are access a map it panics. |
Thank you for the investigation, @TylerHelmuth! |
Closed via open-telemetry/opentelemetry-collector#9595 |
Component(s)
No response
What happened?
Description
Daemonset collector instances have been crashing and restarting when having multiple exporters using the same instance of the
headers_setter
extension. Collectors eventually crash with the following error:fatal error: concurrent map writes
Steps to Reproduce
Expected Result
Collector does not crash
Actual Result
Collector crashes
Collector version
0.94.0
Environment information
Environment
Kubernetes deployment via helm chart version 0.81.1.
Running in AWS/EKS, on Graviton3 processors
OpenTelemetry Collector configuration
Log output
Will add stack trace as comments, as it's 7200 lines long and causes this submission to fail.
Additional context
Have tried duplicating the extension and using the second extension for a second exporter, but still got a crash/restart of the pod.
The text was updated successfully, but these errors were encountered: