[ https://issues.apache.org/jira/browse/KAFKA-9173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002531#comment-17002531 ]
Matthias J. Sax commented on KAFKA-9173: ---------------------------------------- {quote}The second issue is that when 210 partitions are available to consume from, only 10 tasks are created. It is "designed" to behave like that, but I would argue this is not very productive "design" and should be improved. {quote} Feel free to create a new ticket for this case. There might be some corner cases for which we can support this. This ticket is marked as "bug" and we should split both concerns; the new ticket should be am "improvement" ticket. Thanks. > 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: Critical > 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)