Skip to content
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

Span processors / trace exporters should discard traces if they cannot be sent quickly enough #1707

Closed
dobesv opened this issue Dec 1, 2020 · 0 comments · Fixed by #1708
Closed
Assignees
Labels
bug Something isn't working

Comments

@dobesv
Copy link
Contributor

dobesv commented Dec 1, 2020

Currently if you are adding spans to a BatchSpanProcessor or SimpleSpanProcessor faster than they are able to be delivered to the destination, they just accumulate data in memory until the process crashes. Also in this case, they start new HTTP requests before the prior one(s) complete, consuming file descriptors and memory buffers as well.

@dobesv dobesv added the bug Something isn't working label Dec 1, 2020
pichlermarc pushed a commit to dynatrace-oss-contrib/opentelemetry-js that referenced this issue Dec 15, 2023
martinkuba pushed a commit to martinkuba/opentelemetry-js that referenced this issue Mar 13, 2024
martinkuba pushed a commit to martinkuba/opentelemetry-js that referenced this issue Mar 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant