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
don't block when there are no buffers left #1641
Conversation
dd-trace-core/src/main/java/datadog/trace/common/writer/ddagent/DispatchingDisruptor.java
Show resolved
Hide resolved
5b6a772
to
e2c0859
Compare
e2c0859
to
1d79f43
Compare
@@ -114,6 +116,11 @@ public void onScheduleFlush(final DDAgentWriter agentWriter, final boolean previ | |||
// not recorded | |||
} | |||
|
|||
@Override | |||
public void onBackedUpTraceBuffer() { | |||
statsd.incrementCounter("trace.buffer.backlog"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this. This is likely my fault for not reading/understanding the disruptor API better. I assumed WaitStrategy
applied to both producer and consumer, but sadly it seems to be just consumer.
Hmm, yes, we should have thought about the no buffer available case a little more carefully. This seems like a good step in the right direction. |
fa9513e
to
25551ca
Compare
f39e025
to
e2f46a9
Compare
No description provided.