You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an environment with 5 kafka brokers serving 2 topics. I can produce without issues and I can consume without issues with the linux librdkafka client. The problem is with consuming on windows. When I subscribe I never receive any messages. I'm using the RdKafka::KafkaConsumer with Subscribe() and the rebalance_cb defined to a class that seeks based on offset times to the start of the current day.
I'm using a new consumer group each time I launch the application (only one instance).
When I first enabled all debug output I noticed that the metadata requests never returned topic information. I was able to get around that by creating a RdKafka::Topic for each of my topics
Description
No data flowing on windows client.
I have an environment with 5 kafka brokers serving 2 topics. I can produce without issues and I can consume without issues with the linux librdkafka client. The problem is with consuming on windows. When I subscribe I never receive any messages. I'm using the RdKafka::KafkaConsumer with Subscribe() and the rebalance_cb defined to a class that seeks based on offset times to the start of the current day.
I'm using a new consumer group each time I launch the application (only one instance).
When I first enabled all debug output I noticed that the metadata requests never returned topic information. I was able to get around that by creating a RdKafka::Topic for each of my topics
But, I just get fetch backoffs and data never flows
I'm attaching the full log snippet.
kafka_log_925.txt
Other details-
Not using kerbose or any authentication. Not using compression. Compiling with LIBRDKAFKA_STATICLIB defined on windows.
No errors or warning in broker logs
contents of win32_config.h:
librdkafka version v0.11.5
Kafka 1.0.1
Operating system: windows server 2012 r2
librdkafka client configuration:
The text was updated successfully, but these errors were encountered: