Page History

...

While with the new option, the StreamsResetter will force removing all active members fetched by KafkaAdminClient#describeConsumerGroups, and all the members info will be logged out if all removals succeed. Otherwise,  exception the first member removal error will be thrown. Further more, users should make sure all the stream applications should be shutdown when run 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 broker side.

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

...