Open jaysonsantos opened 5 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This still happens on current versions
This is still happening even with providers like Sentry on nodejs
Component(s)
processor/tailsampling
What happened?
Description
After a few days, sometimes weeks, the collector starts to pile up memory and stops receiving spans.
Steps to Reproduce
Keep running the collector for enough time so the memory starts to grow
Expected Result
The memory should be a constant with the number of traces received
Actual Result
The memory never goes down
Collector version
0.89.0
Environment information
Environment
Docker image ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib
OpenTelemetry Collector configuration
Log output
No response
Additional context
This was originally reported on #29762