[
https://issues.apache.org/jira/browse/KAFKA-20848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132174#comment-18132174
]
이선민 commented on KAFKA-20848:
-----------------------------
Thanks [~mjsax]. That makes sense, so I'll keep them as two KIPs and pick up
this one.
The scope I have in mind for this KIP:
* The consumer, share, and streams group heartbeat responses carry the
effective values of the group configs that are relevant to the client, and the
client logs them when it first receives them and whenever they change.
* When a stored group config is capped by the broker bounds, the response
indicates it, so the client can log a warning with both the configured and the
effective value.
Out of scope: the describe output, the alter-config validation (KAFKA-20835),
and updating client behavior automatically. If it's useful, I can file a
separate ticket for the describe output.
I'll share the KIP on the dev list once the draft is ready.
> Consider to surface group-level misconfigurations client side
> -------------------------------------------------------------
>
> Key: KAFKA-20848
> URL: https://issues.apache.org/jira/browse/KAFKA-20848
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer, group-coordinator, streams
> Reporter: Matthias J. Sax
> Priority: Minor
> Labels: needs-kip
> Attachments: analyze.py, run.sh, summary.txt
>
>
> With the new KIP-848 based consumer/share/streams groups, many configs moved
> from the client into the broker.
> Some of these config are sent back to the client (as the client really uses
> them), and we recently started to log them
> ([https://github.com/apache/kafka/pull/22749] and
> [https://github.com/apache/kafka/pull/22730]) for improved observability.
> However, there is a few more configs which have broker defaults plus group
> level overwrites, and they are not visible on the client (only
> describe-config or describe-group would reveal them). At the same time, the
> broker might overwrite group-level config (clamping to min/max for example),
> what is not visible either on the client.
> For Kafka Streams, we have one hybrid config (client + broker combination)
> ([https://github.com/apache/kafka/pull/22213]) and introduced and error code
> in the StreamsHeartbeatResponse to surface a misconfiguration client side.
> The ides of this ticket is, to do a similar thing for _all_ group level
> configs. We would add _all_ effective group config to the HB response for
> logging, with relogging if changed. Additionally, if a value is clamped, and
> the set group-config is not the effective config, we return some error code,
> allowing the client to also log a WARNING about it.
> This would be a protocol change, so thus we need a KIP.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
