-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
0.7 branch can't seem to actually connect to kafka 0.7.0 ? #107
Comments
Hi, Broker addresses Solution: In librdkafka 0.8/master there is no need for this since the same information is gathered automatically directly from the broker without the need for zk. Initial offset Solution:
There is a big difference in functionality between librdkafka 0.7 and 0.8, and while 0.7 is used in some limited production setups, 0.8 is used at big scale (wikipedia for example) and it is where all development happens. |
It is of course feasible to add the required zookeeper support to the application and propagate broker leader information to rdkafka 0.7. |
Closing due to inactivity. Reopen if this is still an issue. |
Hi, I'd like to use librdkafka for consuming from some high volume streams as I'd rather write C instead of Java (and oh god the Java buildchain needed for production...), but the example library can't seem to connect to Kafka 0.7.0
The highlight reel:
[2014-04-22 00:04:07,704] INFO Consumer console-consumer-82345_kafka-yo-kafka-1398125047273-388d7684 selected partitions : rt-san_francisco:0-0: fetched offset = 1402874789: consumed offset = 1402874789 (kafka.consumer.ZookeeperConsumerConnector)
versus% Error: Broker: Offset out of range (0)
[2014-04-22 00:04:07,711] INFO FetchRunnable-0 start fetching topic: rt-san_francisco part: 0 offset: 1402874789 from localhost:9093 (kafka.consumer.FetcherRunnable)
I started to dive into the code, but I'm not entirely familiar with the codebase, so not sure where this error is originating from.
The text was updated successfully, but these errors were encountered: