KAFKA-13301 Config documentation optimized for 'request.timeout. ms' and 'max.poll.interval.ms'. (#11329)

Reviewers: Guozhang Wang <wangguoz@gmail.com>
This commit is contained in:
Weisheng Yang 2021-09-19 13:19:02 +08:00 committed by GitHub
parent 074a3dacca
commit db16c516a7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -1543,9 +1543,9 @@ only support 0.10.1.x or later brokers while 0.10.1.x brokers also support older
<li> The new Java Consumer now supports heartbeating from a background thread. There is a new configuration <li> The new Java Consumer now supports heartbeating from a background thread. There is a new configuration
<code>max.poll.interval.ms</code> which controls the maximum time between poll invocations before the consumer <code>max.poll.interval.ms</code> which controls the maximum time between poll invocations before the consumer
will proactively leave the group (5 minutes by default). The value of the configuration will proactively leave the group (5 minutes by default). The value of the configuration
<code>request.timeout.ms</code> must always be larger than <code>max.poll.interval.ms</code> because this is the maximum <code>request.timeout.ms</code> (default to 30 seconds) must always be smaller than <code>max.poll.interval.ms</code>(default to 5 minutes),
time that a JoinGroup request can block on the server while the consumer is rebalancing, so we have changed its default since that is the maximum time that a JoinGroup request can block on the server while the consumer is rebalance.
value to just above 5 minutes. Finally, the default value of <code>session.timeout.ms</code> has been adjusted down to Finally, the default value of <code>session.timeout.ms</code> has been adjusted down to
10 seconds, and the default value of <code>max.poll.records</code> has been changed to 500.</li> 10 seconds, and the default value of <code>max.poll.records</code> has been changed to 500.</li>
<li> When using an Authorizer and a user doesn't have <b>Describe</b> authorization on a topic, the broker will no <li> When using an Authorizer and a user doesn't have <b>Describe</b> authorization on a topic, the broker will no
longer return TOPIC_AUTHORIZATION_FAILED errors to requests since this leaks topic names. Instead, the UNKNOWN_TOPIC_OR_PARTITION longer return TOPIC_AUTHORIZATION_FAILED errors to requests since this leaks topic names. Instead, the UNKNOWN_TOPIC_OR_PARTITION