THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Use REST API to get list of `group.instance.id` on stream instances user wants to remove
- Shutdown targeting stream instances
- Use command line API to batch remove offline consumers
****Update 04/25****
We are going to let stream user directly configures `group.instance.id`, for the sake of avoiding surprising triggering of static membership. On per thread basis, we will pass in (user configured group.instance.id) + "-thread-" + thread id to make sure each main consumer uses unique instance id within one Kafka Stream instance.
Server Behavior Changes
Join Group Logic Change
...
- Upgrade your broker to include this KIP.
- Upgrade your client to include this KIP.
- Set `group.instance.id` to be unique for each consumer(or stream instance) and `session.timeout.ms` to a reasonable number if necessaryFor KStream user set `client.id` for Stream instances should do the work
- Rolling bounce the consumer group.
...