-
Notifications
You must be signed in to change notification settings - Fork 3.6k
fix: Multiple potential issues with the tcp DNS client #32636
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
Conversation
LGTM |
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.
LGTM
} else { | ||
val oldest = requestBuffer.head | ||
val newRequestBuffer = requestBuffer.tail :+ msg | ||
log.warning("Dropping oldest buffered DNS request [{}] due to TCP backpressure", oldest) |
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.
ok to log the ByteString? anything sensitive in those?
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.
It's the DNS query Message
, I can't think of any way that would be sensitive (and that we don't already log in a ton of places)
* fix: improve TCP DNS client interactions with TCP actor * ensure that TCP connection is closed when TcpDnsClient fails * Fix for potential re-order of response bytes during high load * Deathwatch the connection to make sure we are never stuck in a broken state --------- Co-authored-by: Levi Ramsey <levi.ramsey@alum.cs.umass.edu>
* fix: improve TCP DNS client interactions with TCP actor * ensure that TCP connection is closed when TcpDnsClient fails * Fix for potential re-order of response bytes during high load * Deathwatch the connection to make sure we are never stuck in a broken state --------- Co-authored-by: Johan Andrén <johan@markatta.com> Co-authored-by: Levi Ramsey <levi.ramsey@alum.cs.umass.edu>
Continuation of #32635