-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kafka offset deletion causes reprocessing #180
Comments
Archival has been paused to reproduce this, to be sure it is not due to code issue. |
Found the root cause: lastOffset 1
initialOffset was expected to be 1 but is -2
Doing this #20 will help as we won't depend on Kafka to store the last consumer group last offsets. |
Workaround:
|
Solution could be very simple: Operator watches over the topic having 0 new input for a topic for some time. And stop batcher and loaders for those topics. But this would bring in prometheus dependency, we can do this without it also. |
Related https://issues.apache.org/jira/browse/KAFKA-4682 Kafka by default deletes the offset info for consumer after 7 days. https://www.reddit.com/r/apachekafka/comments/nakg6o/how_to_set_infinite_offset_retention_minutes/ |
Increased the offset.retention.minutes to large value temp fix. |
Batcher data in s3 is getting rotated/archived/deleted sooner than expected 14d. Need to find the root cause and fix it.
Recreate is required everytime this is happening.
pq: Mandatory url is not present in manifest file.
The text was updated successfully, but these errors were encountered: