[
https://issues.apache.org/jira/browse/KAFKA-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raman Gupta updated KAFKA-8789:
-------------------------------
Comment: was deleted
(was: UPDATE: The error message may be coming from the schema registry, which
would put it outside the purview of the Kafka project. Sorry for the noise.
For future Googlers, I created this issue instead:
[https://github.com/confluentinc/schema-registry/issues/1185])
> kafka-console-consumer timeout-ms setting behaves incorrectly with older
> client
> -------------------------------------------------------------------------------
>
> Key: KAFKA-8789
> URL: https://issues.apache.org/jira/browse/KAFKA-8789
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Affects Versions: 2.3.0
> Reporter: Raman Gupta
> Priority: Major
>
> I have a topic with about 20,000 events in it, running on a Kafka 2.3.0
> broker. When I run the following tools command using the older Kafka client
> included in Confluent 5.0.3.
> bin/kafka-console-consumer \
> --bootstrap-server $KAFKA \
> --topic x \
> --from-beginning --max-messages 1 \
> --timeout-ms 15000
> I get 1 message as expected.
> However, when running the exact same command using the console consumer
> included with Confluent 5.3.0, I get
> org.apache.kafka.common.errors.TimeoutException, and 0 messages processed.
> NOTE: I am using the Confluent distribution of Kafka for the client side
> tools, specifically Confluent 5.0.3 and Confluent 5.3.0. I can certainly try
> to replicate with a vanilla Kafka if necessary.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
