Kaffe v1.2.1 Kaffe.GroupMember

Consume messages from a Kafka topic for a consumer group.

The actual consumption is delegated to a series of subscribers, see Kaffe.Subscriber.

The subscribers are assigned generations. Each generation represents a specific configuration. In order to allow the partitions to be rebalanced on startup, there is a delay between receiving a set of assignments associated with that generation and actually creating the subscribers. If a new generation is received in the mean time, the older generation is discarded.

See: https://github.com/klarna/brod/blob/master/src/brod_group_member.erl

Also: https://github.com/klarna/brucke/blob/master/src/brucke_member.erl

The brod_group_member behavior is used.

Summary

Functions

Callback implementation for c::brod_group_member.assign_partitions/3

Callback implementation for c::brod_group_member.assignments_received/4

Callback implementation for c::brod_group_member.assignments_revoked/1

Callback implementation for c::brod_group_member.get_committed_offsets/2

Functions

assign_partitions(pid, members, topic_partitions)

Callback implementation for c::brod_group_member.assign_partitions/3.

assignments_received(pid, member_id, generation_id, assignments)

Callback implementation for c::brod_group_member.assignments_received/4.

assignments_revoked(pid)

Callback implementation for c::brod_group_member.assignments_revoked/1.

get_committed_offsets(group_member_pid, topic_partitions)

Callback implementation for c::brod_group_member.get_committed_offsets/2.

start_link(subscriber_name, consumer_group, worker_manager_pid, topic)