feat: add reconsumer module #93
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Ticket(s)
NA
Checklist
Problem
We sometimes need to reprocess Kafka messages due to some system issue. Sometimes this is an easy offset change to the main consumer group and everything is fine. Other times we need more fine control to limit the time window or topics reconsumed.
Details
This is a WIP PR for how I would imagine Kafka message reconsuming would work. A couple other details:
This could possibly be done with more advanced Kafka stuff like Kafka Streams, however would require a huge amount of work into porting that to Elixir.
We should try to optimize this as much as possible
We want metrics for processing, as well as logs about status
We need to ensure this can be ran on an already existing system (no hard coded module names conflicting)