You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Josh Goodrich (JIRA)" <ji...@apache.org> on 2016/08/24 20:38:20 UTC
[jira] [Created] (KAFKA-4085) Create Consumer fetch(..)
implementation that returns any events available at time of request
Josh Goodrich created KAFKA-4085:
------------------------------------
Summary: Create Consumer fetch(..) implementation that returns any events available at time of request
Key: KAFKA-4085
URL: https://issues.apache.org/jira/browse/KAFKA-4085
Project: Kafka
Issue Type: Improvement
Components: clients
Reporter: Josh Goodrich
The current implementation of the KafkaConsumer.poll(long timeout) does not always return events, even if new events are available on the cluster. I believe this is due to the Consumer not yet syncing all of it's metadata (topics, partitions, offsets, etc . . .) and reaching the timeout before even getting to see if there are events that match it's request.
The Consumer should have a fetch(..) method that guarantees to return events if there are available events in Kafka that meet it's configured criteria. The current poll(..) has unpredictable results depending on how quickly the Consumer can synch with the Broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)