[
https://issues.apache.org/jira/browse/KAFKA-9173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988196#comment-16988196
]
Guozhang Wang commented on KAFKA-9173:
--------------------------------------
[~o.muravskiy] Sorry that I did not make myself clearer before, I meant to say
"maximum num.partitions across the input topic(s)", rather not "sum of
num.partitions". So in your case since all topics have 10 partitions each, the
"max" of it is still 10; if you have a topic which has, say 11 partitions, then
the "max" is 11 and the num.tasks would be 11.
> StreamsPartitionAssignor assigns partitions to only one worker
> --------------------------------------------------------------
>
> Key: KAFKA-9173
> URL: https://issues.apache.org/jira/browse/KAFKA-9173
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Oleg Muravskiy
> Priority: Major
> Labels: user-experience
> Attachments: StreamsPartitionAssignor.log
>
>
> I'm running a distributed KafkaStreams application on 10 worker nodes,
> subscribed to 21 topics with 10 partitions in each. I'm only using a
> Processor interface, and a persistent state store.
> However, only one worker gets assigned partitions, all other workers get
> nothing. Restarting the application, or cleaning local state stores does not
> help. StreamsPartitionAssignor migrates to other nodes, and eventually picks
> up other node to assign partitions to, but still only one node.
> It's difficult to figure out where to look for the signs of problems, I'm
> attaching the log messages from the StreamsPartitionAssignor. Let me know
> what else I could provide to help resolve this.
> [^StreamsPartitionAssignor.log]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
