[
https://issues.apache.org/jira/browse/KAFKA-20835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102040#comment-18102040
]
Yunseop Eom commented on KAFKA-20835:
-------------------------------------
[~mjsax]
Thank you for the feedback. I understand that I opened too many AI-assisted PRs
in a short period, including for issues that were already assigned or in
progress. I apologize for the noise and for not checking ownership and WIP
status carefully enough.
Going forward, I will focus on a small number of issues that I personally
understand, verify the assignee and WIP status before starting work, and open a
PR only after thoroughly reviewing the design, implementation, and tests. I
will also follow Kafka's contribution and PR conventions more carefully.
For KAFKA-20835, I will not make further changes while the KIP/design work is
in progress, and I would be happy to participate in the KIP review.
> 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)
