ConsumerConfig
Related Docs:
object ConsumerConfig
| package consumer
if true, periodically commit to zookeeper the offset of messages already fetched by the consumer
the frequency in ms that the consumer offsets are committed to zookeeper
Client id is specified by the kafka consumer client, used to distinguish different clients
consumer id: generated automatically if not set.
consumer id: generated automatically if not set. Set this explicitly for only testing purpose.
throw a timeout exception to the consumer if no message is available for consumption after the specified interval
If you are using "kafka" as offsets.storage, you can dual commit offsets to ZooKeeper (in addition to Kafka).
If you are using "kafka" as offsets.storage, you can dual commit offsets to ZooKeeper (in addition to Kafka). This is required during migration from zookeeper-based offset storage to kafka-based offset storage. With respect to any given consumer group, it is safe to turn this off after all instances within that group have been migrated to the new jar that commits offsets to the broker (instead of directly to ZooKeeper).
Whether messages from internal topics (such as offsets) should be exposed to the consumer.
the number of byes of messages to attempt to fetch
the minimum amount of data the server should return for a fetch request.
the minimum amount of data the server should return for a fetch request. If insufficient data is available the request will block
the maximum amount of time the server will block before answering the fetch request if there isn't sufficient data to immediately satisfy fetch.min.bytes
a string that uniquely identifies a set of consumers within the same consumer group
the number threads used to fetch data
backoff time to reconnect the offsets channel or to retry offset fetches/commits
socket timeout to use when reading responses for Offset Fetch/Commit requests.
socket timeout to use when reading responses for Offset Fetch/Commit requests. This timeout will also be used for the ConsumerMetdata requests that are used to query for the offset coordinator.
Retry the offset commit up to this many times on failure.
Retry the offset commit up to this many times on failure. This retry count only applies to offset commits during shut-down. It does not apply to commits from the auto-commit thread. It also does not apply to attempts to query for the offset coordinator before committing offsets. i.e., if a consumer metadata request fails for any reason, it is retried and that retry does not count toward this limit.
Specify whether offsets should be committed to "zookeeper" (default) or "kafka"
Select a strategy for assigning partitions to consumer streams.
Select a strategy for assigning partitions to consumer streams. Possible values: range, roundrobin
max number of message chunks buffered for consumption, each chunk can be up to fetch.message.max.bytes
backoff time between retries during rebalance
max number of retries during rebalance
backoff time to refresh the leader of a partition after it loses the current leader
the socket receive buffer for network requests
the socket timeout for network requests.
the socket timeout for network requests. Its value should be at least fetch.wait.max.ms.
ZK host string
ZK host string
the max time that the client waits to establish a connection to zookeeper
the max time that the client waits to establish a connection to zookeeper
zookeeper session timeout
zookeeper session timeout
how far a ZK follower can be behind a ZK leader
how far a ZK follower can be behind a ZK leader