queue, such that it says "X consumers" whereas the reality is "X - N
consumers" where N>0. This seems to be triggered by disagreement as to
the state of sockets, likely caused by an unclean disconnect by a
client. This could be caused by any number of things, such as
rebooting on of our client VMs or maybe just a connection drop inside
our providers network (a common and unwelcome event).
We've seen this problem on 2.5.1 + R14B01, and are continuing to see
it on 2.7.1 + R15B. I can try to provide additional details on
My concerns on consumer counts are two-fold. First, we have no way to
validate that num_procs==num_consumers, an important metric when
validating that our platform is running correctly. Second, we don't
know if rabbit is pushing messages to these ghost consumers, and if
so, what's happening to them.
Senior Software Engineer
Troy, NY 12180
aaron at agoragames.com