[
https://issues.apache.org/jira/browse/KAFKA-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272901#comment-17272901
]
feyman commented on KAFKA-9689:
-------------------------------
The version detection flow leveraging the versioning system is as described in
the section: Use case: {{group_coordinator}} feature flag in KIP-584.
The code change mainly contains 3 parts:
1) StreamThread should know if itself is leader in the consumer group, if yes,
it should periodically query the describeFeatures api to see if there are
feature metadata updates
2) There should be some place to put the feature metadata in the
MemberMetadata, either in the assignment(userData) or add a new field in the
MemberMetadata(which involves public interface change).
3) the StreamThread should dynamically switch to the new thread producer
without affecting the existing tasks that
> Automatic broker version detection to initialize stream client
> --------------------------------------------------------------
>
> Key: KAFKA-9689
> URL: https://issues.apache.org/jira/browse/KAFKA-9689
> Project: Kafka
> Issue Type: New Feature
> Reporter: Boyang Chen
> Assignee: feyman
> Priority: Major
>
> Eventually we shall deprecate the flag to suppress EOS thread producer
> feature, instead we take version detection approach on broker to decide which
> semantic to use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
