You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2018/02/24 04:08:00 UTC
[jira] [Resolved] (KAFKA-6328) Exclude node groups belonging to
global stores in InternalTopologyBuilder#makeNodeGroups
[ https://issues.apache.org/jira/browse/KAFKA-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-6328.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
> Exclude node groups belonging to global stores in InternalTopologyBuilder#makeNodeGroups
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-6328
> URL: https://issues.apache.org/jira/browse/KAFKA-6328
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Guozhang Wang
> Assignee: Richard Yu
> Priority: Major
> Labels: newbie
> Fix For: 1.1.0
>
> Attachments: kafka-6328.diff
>
>
> Today when we group processor nodes into groups (i.e. sub-topologies), we assign the sub-topology id for global tables' dummy groups as well. As a result, the subtopology ids (and hence task ids) are not consecutive anymore. This is quite confusing for users trouble shooting and debugging; in addition, the node group for global stores are not useful as well: we simply exclude it in all the caller functions of makeNodeGroups.
> It would be better to simply exclude the global store's node groups in this function so that the subtopology ids and task ids are consecutive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)