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

Error Threshold Limits should cause topic shutdowns instead of service shutdowns #25

Open
dmvt opened this issue Jan 6, 2015 · 0 comments
Assignees

Comments

@dmvt
Copy link
Contributor

dmvt commented Jan 6, 2015

Dan Matthews [1:32 PM]
perhaps per topic shutdowns would work better?

G™eoff L™anotte [1:32 PM]
that is agood idea

Ryan Williams [1:32 PM]
yeah, that'd be good a way to isolate them

Dan Matthews [1:32 PM]
Shouldn't be too hard to tackle once we're clear of the TSL stuff

Ryan Williams [1:33 PM]
I suppose that was the advantage of the "error" topic in the old emque

Ryan Williams [1:33 PM]
a way to move past bad ones

Ryan Williams [1:33 PM]
but, we can't ignore them, so the per topic shutdown seems better

Dan Matthews [1:33 PM]
yeah... though we did decide we wanted to halt processing instead of moving to the next msg

Dan Matthews [1:34 PM]
exactly

Dan Matthews [1:34 PM]
can just drop # of workers on the topic to 0 and then notify slack

@dmvt dmvt self-assigned this Jan 6, 2015
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

1 participant