[
https://issues.apache.org/jira/browse/KAFKA-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-8548.
------------------------------------
Resolution: Not A Problem
Closing this. The docs are correct as pointed out by [~ckamal].
> Inconsistency in Kafka Documentation
> ------------------------------------
>
> Key: KAFKA-8548
> URL: https://issues.apache.org/jira/browse/KAFKA-8548
> Project: Kafka
> Issue Type: Task
> Components: documentation
> Affects Versions: 2.2.1
> Reporter: Seweryn Habdank-Wojewodzki
> Priority: Minor
>
> Dears,
> Two parts (referenced below) of [documentation
> |http://kafka.apache.org/documentation/] are not quite consistent.
> In one text we can read, that max.poll.interval.ms has defaut value
> Integer.MAX_VALUE, in the other it is 300 000.
> Part 1.
> {quote}
> The default values for two configurations of the StreamsConfig class were
> changed to improve the resiliency of Kafka Streams applications. The internal
> Kafka Streams producer retries default value was changed from 0 to 10. The
> internal Kafka Streams consumer max.poll.interval.ms default value was
> changed from 300000 to {color:#FF0000}Integer.MAX_VALUE{color}.
> {quote}
>
> Part 2. - Table
> |max.poll.interval.ms|The maximum delay between invocations of poll() when
> using consumer group management. This places an upper bound on the amount of
> time that the consumer can be idle before fetching more records. If poll() is
> not called before expiration of this timeout, then the consumer is considered
> failed and the group will rebalance in order to reassign the partitions to
> another member.|int|{color:#FF0000}300000{color}|[1,...]|medium|
> Which value is then default :-)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
