[
https://issues.apache.org/jira/browse/KAFKA-20835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101493#comment-18101493
]
Matthias J. Sax commented on KAFKA-20835:
-----------------------------------------
[~chia7712] – Is this PR reasonable to begin with? I didn't take a look, but
[~lh0156] did open like 20 PRs over night, and I just closed to others, as they
are clearly low quality AI slop... Just wanted to bring it to your attention.
[~lh0156] – As said on other replies – we do appreciate AI assisted PRs, but we
still require high quality PRs, and you need to ensure as a contributor to
fully understand the changes before you open a PR, and you should also respect
if tickets are already assigned, and refrain from opening PR for tickets that
are already WIP.
> Group-level alter-config RPC fails, if single group config is invalid
> ---------------------------------------------------------------------
>
> Key: KAFKA-20835
> URL: https://issues.apache.org/jira/browse/KAFKA-20835
> Project: Kafka
> Issue Type: Bug
> Components: group-coordinator
> Reporter: Matthias J. Sax
> Assignee: Chia-Ping Tsai
> Priority: Minor
>
> ControllerConfigurationValidator gets the full post-alter override map, not
> just the altered keys. So if a broker bound is narrowed after an override was
> set, GroupConfig.validate() rejects the stale value on every later alter –
> even one that doesn't touch it.
> Repro: set consumer.session.timeout.ms=90000 on a group, restart controller
> with group.consumer.max.session.timeout.ms=60000, then try to alter
> consumer.heartbeat.interval.ms on the same group -> INVALID_CONFIG on the
> session timeout.
> Impact: the group is stuck until the stale key is fixed or deleted.
> Validation is all-or-nothing per resource, and throws on the first violation,
> so multiple stale keys must all be repaired in one request, discovered one
> error at a time.
> It seems LogConfig may have a similar issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
