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
Using the broker on a large deployment, we see some service consumers take too many connection to reach their host, saturating the rabbit broker and preventing other users to access their vhost.
RabbitMq offers per vhost max connection.
Could the broker assign this max conn value when creating the vhost ?
The text was updated successfully, but these errors were encountered:
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Using the broker on a large deployment, we see some service consumers take too many connection to reach their host, saturating the rabbit broker and preventing other users to access their vhost.
RabbitMq offers per vhost max connection.
Could the broker assign this max conn value when creating the vhost ?
The text was updated successfully, but these errors were encountered: