Differentiate producer/consumer configuration #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The producer/consumer code was sharing the same configuration, which means the producer was being initialized as a consumer as well. If the producer starts first, it joins the same group and is assigned the only partition for the topic. When the consumer eventually comes online, it joins the group but is not assigned the partition, appearing to be stuck. This patch bifurcates the configuration on whether or not the Kafka client being stood up should be a consumer. Also, the PR adds a few hygienic options that should always be set for consumers (read committed, require stable offsets).