Page History

...

As we see, the metadata exposed contains member.id, group.instance.id and generation.id, which are essentially the identifiers we use in the normal offset commit protocol. Inside `TxnOffsetCommitRequest`, member.id and To be able to keep track of the latest metadata information, we will add another callback function to the ConsumerRebalanceListener:

public interface ConsumerRebalanceListener {
	...
	default void onGroupRejoined(ConsumerGroupMetadata consumerGroupMetadata) {
	 	// no-op
    } 
}

So that EOS users could get refreshed group metadata as needed.

To pass the information to broker, member.id, group.instance.id generationid and generation.id field shall be added to make the to `TxnOffsetCommitRequest`,  which makes txn offset commit fencing consistent with normal offset fencing. 

...