[
https://issues.apache.org/jira/browse/KAFKA-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057518#comment-18057518
]
Andrew Schofield commented on KAFKA-20162:
------------------------------------------
Please go ahead.
> Validation and enforcement of group configurations
> --------------------------------------------------
>
> Key: KAFKA-20162
> URL: https://issues.apache.org/jira/browse/KAFKA-20162
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Andrew Schofield
> Assignee: majialong
> Priority: Major
>
> Part of KIP-1240.
> * Tighten up and correct the validation and enforcement of existing group
> configurations such as group.consumer.session.timeout.ms.
> * When a broker is restarted, static broker configurations are applied. It is
> possible that the group configurations might now lie outside the broker
> limits. In some cases, this causes the broker not to start.
> * When a group configuration is updated, the value is validated against the
> broker configuration limits. If the validation fails, the request is
> rejected. (No change)
> * When a broker configuration is updated, the existing group configurations
> are not validated. There are no cascading checks of all of the group
> configurations. This ensures that the administrator is able to tighten or
> relax limits easily.
> * When a broker starts, if a group configuration lies outside the broker
> configuration limits, the broker is permitted to start. The broker writes a
> log line indicating that a group configuration was outside the broker limits,
> and that the effective value will be within the broker limits.
> * When a group configuration is evaluated, the effective value of a group
> configuration is capped by the broker limits.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
