[
https://issues.apache.org/jira/browse/KAFKA-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram updated KAFKA-2603:
----------------------------------
Status: Patch Available (was: Open)
The PR adds a new argument -timeout-ms with the same semantics as
consumer.timeout.ms in the old consumer. The new arg is supported with both old
and new consumer.
The ducktape ConsoleConsumer service uses the new arg instead of setting
timeout in the consumer config file so that it can be used with both the old
and new consumer.
> Add timeout to ConsoleConsumer running with new consumer
> --------------------------------------------------------
>
> Key: KAFKA-2603
> URL: https://issues.apache.org/jira/browse/KAFKA-2603
> Project: Kafka
> Issue Type: Test
> Affects Versions: 0.9.0.0
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: 0.9.0.0
>
>
> ConsoleConsumer exits when no messages are received for a timeout period when
> run with the old consumer since the old consumer had a timeout parameter.
> This behaviour is not available with the new consumer and hence ducktape
> tests which rely on the timeout cannot be run with the new consumer.
> [~granders] has suggested a solution in KAFKA-2581.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
