Status

Current state:  AcceptedVoting

Vote thread: [Vote] KIP-571: Add option to force remove members in StreamsResetter

...

While with the new option, the StreamsResetter will force remove all active members fetched by KafkaAdminClient#describeConsumerGroups, and all the members' info will be logged out if all removals succeed. Otherwise,  the first member removal error will be thrown. Furthermore, users should make sure all the stream applications are shutdown when running StreamsResetter with --force, otherwise it might trigger unexpected rebalance. 

The detailed member removal error cases could be found in KIP-345, which introduced static membership and batch removal on the broker side.

Broker side logic has no change, GroupCoordinator#handleLeaveGroup can handle both dynamic and static member removals since 2.4.

Operational steps of the StreamsResetter:

1. Stop all the consumers (of streams instances), and wait until the shutdown is complete, otherwise, unexpected rebalance will be triggered.
2. Use StreamsResetter with --force in case the stopped consumers are still registered at the broker side, without --force, we need to wait for session timeout. 

Compatibility, Deprecation, and Migration Plan

...