-
Notifications
You must be signed in to change notification settings - Fork 324
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
TLS error: 268435703:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER #932
Comments
Hi @nflaig this seems to be more involved than it seems to deploy Kafka on top of a Service Mesh. Have you seen this pattern deployed successfully elsewhere? |
Hi @david-yu, I've seen a similar issue when scraping services with Prometheus within the service mesh. The similarity here is that in both cases the services are dialed directly so maybe the issue is related to that.
I would expect that to be a common thing to be honest but I think it is not really about kafka it seems to be a general issue with dialed directly and stateful sets. |
Related issue with Kafka on Consul K8s: hashicorp/consul#14125 also it is recommended to set MaxInboundConnections to a higher number than defaults which should be enabled by Consul 1.13.2 and #1437 when it is released. |
I think I'm running into the same issue with services deployed by Nomad. I can't get a simple tcp echo server to work. |
Community Note
Overview of the Issue
We are running Kafka and Zookeeper inside the Consul service mesh and sometimes the connection from Kafka to Zookeeper seems to fail. This issue seems to be specific to stateful sets as I also noticed a similar issue when connection to Redis. Also another strange behavior maybe related to this is that the headless service has to be used as the host instead of the normal service. Using the normal service works sometimes but fails more often then the headless service.
Kafka is dialing Zookeeper directly through the headless service so I have configured
ServiceDefaults
to allow direct connections.Another maybe interesting fact is that in the Consul UI Topology view, Zookeeper is not shown as an upstream for Kafka. This always seems to be the case if the connection also does not work so it could potentially be related.
Configuration
Consul helm values
Kafka config related to Consul
Zookeeper config related to Consul
Logs
Zookeeper Envoy logs
Zookeeper logs
Kafka Envoy logs
Kafka logs
Environment details
v0.37.0
v0.37.0
v1.10.4
v1.18.4
v1.20.7
Related
The text was updated successfully, but these errors were encountered: