-
Notifications
You must be signed in to change notification settings - Fork 564
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
fix event lost #1083
base: main
Are you sure you want to change the base?
fix event lost #1083
Conversation
b932fb8
to
e2dd0d9
Compare
e2dd0d9
to
03b52ae
Compare
@ningmingxiao I have not been involved in this repo for about a decade, it's not really professional to tag people here. Will leave this to others. |
sory,but thank you anyway. |
Thanks for contributing! This is a big change that can lead to slow consumers hanging. I recommend either making sure your caller is always fast enough to consume the events, or putting the new behavior behind a knob. |
sometimes I can't make sure consumers run faster, if run plenty of containers, will generate many events, channel will be filled. At least we should let user know event is dropped when chan is filled. |
Can you add a knob in that case? |
Could you describe it in more detail? Thank you |
@ningmingxiao I imagine we'd have a new option when adding the listener. Internally the listener would become some struct with the channel + some listening options, and externally we'd probably need to have versions of |
sometimes if listener chan is full,event will lost.
@fsouza @bufdev
can you review my pr? thank you