-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Key Error: Single Broker #183
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
Comments
How long was it between when you created the topic and you ran the python script?
|
Hi Guys, thanks for the quick response:
@wizzat it was a couple minutes initially and I've restart the script over the past 24 hours a few times to test different things |
Actually, I'm looking at your stack trace and I'm seeing gevent in place. Does the error happen without gevent? I remember that we had a gevent pull request that the author never could get to pass the test suite. |
@wizzat I did it in REPL and was able to replicate it:
I also put that ensure_topic_exists function in from #174 and it fixed the exception but I continuously get client WARNING No partitions for test I want too mention to that this was working in a vagrant environment on a local VM setup with a single broker and single zookeeper but I don't understand why the topology change would affect the code. EDIT: Adding debug logging around the load_metadata function
It looks like the client is getting an empty dictionary for partitions even though the kafka-topics.sh describe command says they exist? |
Are you absolutely sure you're connecting to the same Zookeeper that your Kafka cluster is connecting to? |
@wizzat I doubled checked the ips and everything matches however I just tried running the Java producer that ships with kafka and got some errors:
So the python clients implementation is in line with the Java one so I'll close and figure out why I'm receiving this LeaderNotAvailableException on the cluster. |
Hi, I think this is related to #113, #150, #174. I'm prototyping a kafka environment with a single broker and 3 node zookeeper cluster. I installed the master version since this was a known issue but I'm still getting a key error when producing messages with SimpleProducer.
This cluster just had the topic created with the command line tool and here is the describe:
Error:
Connect Code:
Send Code:
The text was updated successfully, but these errors were encountered: