docs(ecosystem): add Kafka SASL_SSL PTR-lookup troubleshooting guide#810
Open
chideat wants to merge 1 commit into
Open
docs(ecosystem): add Kafka SASL_SSL PTR-lookup troubleshooting guide#810chideat wants to merge 1 commit into
chideat wants to merge 1 commit into
Conversation
Add a solution guide for Kafka SASL_SSL connections that are slow or time out due to reverse DNS (PTR) lookups on the broker connection path (KAFKA-8562), covering diagnosis (listener/accept-queue/thread-dump/DNS-latency checks) and a CoreDNS reverse-zone fix that returns fast NXDOMAIN for unknown Pod addresses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a solution guide for Kafka
SASL_SSLconnections that are slow or time out because the broker performs a synchronous reverse DNS (PTR) lookup on the peer IP while registering each new connection (KAFKA-8562). When unknown Pod/CNI/SNAT addresses have no PTR record and CoreDNS forwards the query to an unreachable upstream, the broker's network processor threads block, the accept queue saturates, and clients see slow connects, metadata timeouts, and repeatedSSL handshake failedmessages.The guide covers:
SASL_SSLchannel-builder path triggers the lookup, and why the peer IP is the post-SNAT source address.ssand/proc/net/tcp), FD/JVM exclusion, JVM thread dumps, reverse-DNS latency measurement, and CoreDNS resolution-flow inspection.NXDOMAIN, with backup, validation, and rollback steps.Verification
All external claims were cross-checked against authoritative sources before merge:
SaslChannelBuilder.buildTransportLayercallinggetHostName()with no client/server guard) and fix PR KAFKA-8562: SaslChannelBuilder - avoid (reverse) DNS lookup while building underlying SslTransportLayer apache/kafka#10059.kafka-versions.yamlat the0.25.0tag.fallthrough, zone authority, andforward/hostsbehavior — CoreDNS plugin docs and source.🤖 Generated with Claude Code