Page History

...

In this pull request, we did an experimental approach to materialize member id(the identity given by broker, equivalent to the member.name in proposal) on the instance local disk. This approach could reduce the rebalances as expected, which is the experimental foundation of KIP-345. However, KIP-345 has a few advantages over it:

1. It gives users more control of their member id stringname; this would help for debugging purposes.
2. It is more cloud-/k8s-and-alike-friendly: when we move an instance from one container to another, we can copy the member id name to the config files.
3. It doe not require the consumer to be able to access another dir on the local disks (think your consumers are deployed on AWS with remote disks mounted).
4. By allowing consumers to optionally specifying a member idname, this rebalance benefit can be easily migrated to connect and streams as well which relies on consumers, even in a cloud environment.

...