You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The queue is emitting a consumer_closed event for every consumer, not just those associated with the channel. This doesn't lead to incorrect behaviour because the management plugin doesn't find the "wrong" consumers to delete since they have the wrong channel pid, but we do more work than needed. O(n^2) in fact :-(
The text was updated successfully, but these errors were encountered:
…f them.
This was not noticed for a long time because the only use of those ctags
was to emit consumer_deleted events which were handled by the management
database, and it ignored invalid {channel, ctag} combinations.
However, it did end up doing more work - and closing n channels out
of m became O(nm) instead of just O(n). References #86.
See https://groups.google.com/d/msg/rabbitmq-users/nvCFKJ0HWH0/pbuNVKM3beoJ
The queue is emitting a consumer_closed event for every consumer, not just those associated with the channel. This doesn't lead to incorrect behaviour because the management plugin doesn't find the "wrong" consumers to delete since they have the wrong channel pid, but we do more work than needed. O(n^2) in fact :-(
The text was updated successfully, but these errors were encountered: