[
https://issues.apache.org/jira/browse/KAFKA-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916165#comment-16916165
]
Sophie Blee-Goldman commented on KAFKA-8831:
--------------------------------------------
[~vinoth] Just to clarify, do you delete all topics, then run the reset tool,
then recreate (only) the input topics? And are you also wiping the state
(either manually or with KafkaStreams#cleanUp)?
> Joining a new instance sometimes does not cause rebalancing
> -----------------------------------------------------------
>
> Key: KAFKA-8831
> URL: https://issues.apache.org/jira/browse/KAFKA-8831
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Chris Pettitt
> Assignee: Chris Pettitt
> Priority: Major
> Attachments: StandbyTaskTest.java, fail.log
>
>
> See attached log. The application is in a REBALANCING state. The second
> instance joins a bit after the first instance (~250ms). The group coordinator
> says it is going to rebalance but nothing happens. The first instance gets
> all partitions (2). The application transitions to RUNNING.
> See attached test, which starts one client and then starts another about
> 250ms later. This seems to consistently repro the issue for me.
> This is blocking my work on KAFKA-8755, so I'm inclined to pick it up
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
