Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To make sure we could recover from broker failure/leader transition, an in-memory member name map is not enough. We will init another topic called `static_member_map` in the cluster and each time we have a stable state we should write the complete mapping information as a single message into it. We could otherwise would reuse the `_consumer_offsets` topic to store this information, which however could be unfavorable if we are making too many changes to existing offset message schema. Either way when the static member map information. When another broker takes over the leadership, we could transfer the mapping together.

...

command line APIs for membership management

For the very first version, we hope to make membership transferring logic and human handling simple enough. We will define three admin command line APIs to help us better manage the groups:

...

  1. the broker is on an old version. 
  2. if the group is preparing rebalance/completing rebalance.
  3. Any member within the current group has not set `member.name`
  4. other potential failure cases.

...