confluent-kafka-go | Confluent 's Apache Kafka Golang client | Pub Sub library

Modules are defined by their go.mod file. Without a go.mod file, it is not a module.

See this from the Go Modules Reference

A module is a collection of packages that are released, versioned, and distributed together. Modules may be downloaded directly from version control repositories or from module proxy servers.

A module is identified by a module path, which is declared in a go.mod file, together with information about the module's dependencies. The module root directory is the directory that contains the go.mod file.

And

A module is defined by a UTF-8 encoded text file named go.mod in its root directory.

Within a consumer group, each partition is consumed by a single consumer. When consumers join the group, one of them computes the assignment which consists of the list of partitions each consumer will handle.

In your client, this can be configured via partition.assignment.strategy. This defaults to range which follows the implementation of Apache Kafka's RangeAssignor.

Quoting the Javadoc:

The range assignor works on a per-topic basis. For each topic, we lay out the available partitions in numeric order and the consumers in lexicographic order. We then divide the number of partitions by the total number of consumers to determine the number of partitions to assign to each consumer. If it does not evenly divide, then the first few consumers will have one extra partition.

For example, suppose there are two consumers C0 and C1, two topics t0 and t1, and each topic has 3 partitions, resulting in partitions t0p0, t0p1, t0p2, t1p0, t1p1, and t1p2.

The assignment will be:

According to the documentation for Producer.Events(), it returns a channel.

Ranging over a channel only terminates when the channel is closed. See the tour of Go for more details.

I can confirm that using the musl build tag works:

Alright, here goes the solution, 1. Since the consumer go routine should live as long as the main go routine is alive and the main go routine is also an endless go routine, closing the consumer go routine while the go routine is running, isn't the correct approach.

So the following solution works