Memory leak in OT Tracing 0.4.1 / 0.6.1 about newrelic-telemetry-sdk-java HOT 2 CLOSED

Hi @mrjaekim .

Thanks for sharing your experience with us...it sounds a lot like #189 and like an unusual case where the communication was down for an extended period of time (not just a network blip). Do you have any idea what was failing? Did anything interesting happen with the network or firewall or DNS or proxies or routes or anything else at that time? Was there any other indication in the logs about why things were failing?

For the sake of discussion, I would like to entertain the idea of allowing data over a certain size to
"age-out" of the buffer. That is, if you've buffered more than spans, the oldest will be replaced when new spans are being buffered. This approach should serve to keep the memory usage constrained, at the cost of potential data loss.

Do you have a sense of how many spans were being buffered to give the 10.77GB size? Do you have a sense of what might be a reasonable number of spans to buffer?

from newrelic-telemetry-sdk-java.

Well, this got auto closed...but it would be great if you could try out the snapshot and let us know if this does genuinely help your problem. Thanks!

from newrelic-telemetry-sdk-java.