Skip to content
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

Copying failing events from DLT to main Topic causes infinite loop #1377

Closed
NickWel opened this issue Feb 14, 2023 · 1 comment · Fixed by #1612
Closed

Copying failing events from DLT to main Topic causes infinite loop #1377

NickWel opened this issue Feb 14, 2023 · 1 comment · Fixed by #1612
Labels
bug Something isn't working good first issue Good for newcomers topic data Kafka Topic data

Comments

@NickWel
Copy link

NickWel commented Feb 14, 2023

When using the "copy topic" function to copy an event from the DLT to the main topic this causes an infinite loop if the event immediatly fails and is republished to the DLT again.

The "copy topic" function seems to also copy any new events that are published to the topic after the copy action has started. If new events are published to this topic faster than these can be copied this copy action never ends.

This issue can be reproduced reliably by creating two topics with a service consuming events from one topic and publishing the same events to the other topic. Manually add 4 events to the second topic and start the "copy topic" action. Now watch the consumer lag increase rapidly.

@tchiotludo tchiotludo added bug Something isn't working good first issue Good for newcomers topic data Kafka Topic data labels Feb 14, 2023
@tchiotludo
Copy link
Owner

The bug is here. We need to fetch the offset of the source top at first and stop after reaching this offset.
PR are welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers topic data Kafka Topic data
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants