...
KIP-571 plan to support the ability to force removing delete members in StreamsResetter, this basically involves 2 public interfaces changes as below:
...
Previously the org.apache.kafka.clients.admin.KafkaAdminClient#removeMembersFromConsumerGroup only support to remove members by specifying the groupInstanceId, which means it only support remove static members, so the memberId is added to support removing dynamic members . Since there are two String fields now, new constructor is added and the old constructor will be deprecated.
2) Add cmdline option --force force to StreamsResetter
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 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.
...
- Because no classes/method will be removed but only deprecated, this change will be backward compatible
- The new added cmdline option --force force is also backward compatible because it's new feature, if not specified, the StreamsResetter's behaviour remains unchanged.
Requirement to use this feature:
Release version requirement | Expected behavior if |
---|
requirement not satisfied | ||
---|---|---|
broker side | >= 2.3 | org.apache.kafka.common.KafkaException: Unknown group metadata version 3 |
client side | update to this KIP |
force is not a recognized option |
Rejected Alternatives
None
...