AndrewJSchofield commented on PR #18738: URL: https://github.com/apache/kafka/pull/18738#issuecomment-2621876464
@asorian0 Thanks for the PR. This proposes a change to the public API (because it changes `MemberToRemove`) which means that it would require a very small KIP to get approval to make the change. I am not a complete expert on this but I would say that it is intentional to provide the group instance ID. This signifies a static group member which means that it can leave and rejoin without losing its place in the group, essentially minimising churn when the member restarts. As a result, you might want to remove the static member administratively if you know it's stopped permanently. You could start a discussion on the Kafka dev mailing list to see whether there's interest in making the change to permit dynamic group members to be removed in the same way. Alternatively, you could create a KIP and start the discussion that way. Hope this helps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
