You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "highluck (Jira)" <ji...@apache.org> on 2020/07/30 16:09:00 UTC

[jira] [Commented] (KAFKA-10283) Consolidate client-level and consumer-level assignment within ClientState

    [ https://issues.apache.org/jira/browse/KAFKA-10283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168029#comment-17168029 ] 

highluck commented on KAFKA-10283:
----------------------------------

[~guozhang] 
Can I pick this issue?

Is there any structure you think of?

> Consolidate client-level and consumer-level assignment within ClientState
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-10283
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10283
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Priority: Major
>              Labels: newbie++
>
> In StreamsPartitionAssignor, we do a two-level assignment, one on the client-level, and then after the assignment is done we further decide within the client how to distributed among consumers if there are more.
> The {{ClientState}} class is used for book-keeping the assigned tasks, however it is only used for the first level, while for the second level it is done outside of the class and we only keep track of the results in a few maps for logging purposes. This leaves us with a bunch of hierarchical maps, e.g. some on the client level and some on the consumer level.
> We would like to consolidate some of these maps into a single data structure for better keeping track of the assignment information, and also for less bug vulnerability causing the assignment information to be inconsistent. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)