Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
k8s/EKS some Proxies fail to get Broker info from Zookeeper
See original GitHub issue
1 - seeing a lot of these errors during cluster init
2 - this is a response to e.g. bin/pulsar-admin topics list cb/test, which on the console returns HTTP 403 Forbidden
This only happens on 1 or 2 out of 4 total Proxies in the cluster. The healthy Proxies return a correct response.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
kafka unable to register brokers in zookeeper when we ...
By overwriting the component variable, the broker will no longer start. The rest proxy needs a broker.
Read more >The Pulsar proxy
The Pulsar proxy is an optional gateway that you can run in front of the brokers in a Pulsar cluster. We recommend running...
Read more >Why Can't I Connect to Kafka? | Troubleshoot Connectivity
I'm going to read some messages! The broker returns metadata, which includes the host and port on which all the brokers in the...
Read more >Error: The Cluster ID ### doesn't match stored clusterId (###)
The default location for Kafka to store data in some configuration is /tmp. ... If the configuration of your Kafka and Zookeeper have...
Read more >Specifying connection settings for a subscription ... - IBM
Select either ZooKeeper Server or Kafka REST Proxy as the communication method for ... To do so, add the broker list to the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same issue happens for me with 2.4.2 cluster. Proxies don’t work until manual restart.
The approach is great. A small improvement you can make is to change
-ge {{ .Values.broker.replicaCount }}to-ge 1.