[
https://issues.apache.org/jira/browse/KAFKA-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912537#comment-17912537
]
David Jacot commented on KAFKA-18297:
-------------------------------------
Yeah, the issue is that there is a race condition with this approach as there
is a chance for the member to rejoin before the removal is verified. This is
the main source of the flakiness. Similarly, when we remove all members before
deleting the group, there is the same race condition. In my opinion, the test
is incorrect.
The member removal is mainly meant to remove static members. For the context,
when a static member shutdowns, it does not leave the group. Hence having a way
to remove it makes sense.
> Fix flaky PlaintextAdminIntegrationTest.testConsumerGroups
> ----------------------------------------------------------
>
> Key: KAFKA-18297
> URL: https://issues.apache.org/jira/browse/KAFKA-18297
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Blocker
> Labels: flaky-test, integration-test, kip-848-client-support
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
