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

Graceful handling of :topic_not_found #301

Closed
technomage opened this issue Aug 5, 2018 · 3 comments
Closed

Graceful handling of :topic_not_found #301

technomage opened this issue Aug 5, 2018 · 3 comments

Comments

@technomage
Copy link

We have circumstances where a topic is deleted and recreated, it would be nice to be able to gracefully handle the :topic_not_found error in those cases. Allowing for that in the consumer and an optional callback to ignore would be sufficient. Let me know if this would be acceptable and I can do a pull request.

@joshuawscott
Copy link
Member

Is this in the GenConsumer and related consumer group functionality, or is this the lower level consumer?

@IanVaughan
Copy link
Contributor

I've spotted this as well, and think I might have a solution as part of #298, in which it can be setup to retry attempting to connect to a topic until present.

@technomage
Copy link
Author

I ended up using a module that delays the retry by monitoring the consumer rather than directly placing it in the supervisor tree. This is working for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants