[
https://issues.apache.org/jira/browse/KAFKA-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Brutschy updated KAFKA-20625:
-----------------------------------
Fix Version/s: 4.4.0
> Add StreamsGroupTopologyDescriptionRequestManager and Streams client topology
> push
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-20625
> URL: https://issues.apache.org/jira/browse/KAFKA-20625
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 4.4.0
> Reporter: Alieh Saeedi
> Assignee: Lucas Brutschy
> Priority: Major
> Fix For: 4.4.0
>
>
> StreamsGroupTopologyDescriptionRequestManager: sends
> StreamsGroupTopologyDescriptionUpdate when coordinator is known,
> TopologyDescriptionRequired was set, stored topology is available, member has
> a non-empty MemberId, and no prior request is in-flight. Error handling:
> NOT_COORDINATOR/COORDINATOR_NOT_AVAILABLE → rediscover coordinator, keep
> flag; COORDINATOR_LOAD_IN_PROGRESS → retry; UNKNOWN_MEMBER_ID → clear flag,
> rejoin; all others → clear flag, log WARN. RequestManagers wiring,
> StreamsGroupHeartbeatRequestManager (read TopologyDescriptionRequired from
> response), StreamsRebalanceData (carry topology description + MemberId),
> StreamThread (convert TopologyDescription to wire format), StreamsConfig
> (topology.description.push.enabled, default true). Unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
