Thanks Feyman, will take a look. On Thu, Apr 30, 2020 at 2:09 AM feyman (Jira) <j...@apache.org> wrote:
> > [ > https://issues.apache.org/jira/browse/KAFKA-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096347#comment-17096347 > ] > > feyman commented on KAFKA-9146: > ------------------------------- > > Hi, I have created a new PR and request for review, thanks! > > [https://github.com/apache/kafka/pull/8589] > > > > > Add option to force delete members in stream reset tool > > ------------------------------------------------------- > > > > Key: KAFKA-9146 > > URL: https://issues.apache.org/jira/browse/KAFKA-9146 > > Project: Kafka > > Issue Type: Improvement > > Components: consumer, streams > > Reporter: Boyang Chen > > Assignee: feyman > > Priority: Major > > Labels: newbie > > > > Sometimes people want to reset the stream application sooner, but > blocked by the left-over members inside group coordinator, which only > expire after session timeout. When user configures a really long session > timeout, it could prevent the group from clearing. We should consider > adding the support to cleanup members by forcing them to leave the group. > To do that, > > # If the stream application is already on static membership, we could > call directly from adminClient.removeMembersFromGroup > > # If the application is on dynamic membership, we should > modify adminClient.removeMembersFromGroup interface to allow deletion based > on member.id. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
