I tried the max-queues
virtual host limit but could not get it to work
#13521
-
Describe the bugWe have a rabbitmq cluster, wherein we have defined a limit on Reproduction steps. Expected behaviorQueues should not exceed the limit defined. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@shaileshlaghane this is not a bug report, this is an insult to open source software maintainers. If you cannot be bothered to even mention the set of steps to reproduce — which for this feature should be trivial — we won't bother to spend a second investigating. In fact, we don't even have any details on the RabbitMQ version used. This feature is known to work at scale at a number of RabbitMQ-as-a-Service environments, so without a way to reproduce against |
Beta Was this translation helpful? Give feedback.
-
Given the following limit:
The limit is enforced, as expected: c = Bunny.new(vhost: "github-13521"); c.start
# => #<Bunny::Session:0x5110 [email protected]:5672, vhost=github-13521, addresses=[127.0.0.1:5672]>
ch = c.create_channel
# => #<Bunny::Channel:12168 @id=1 @connection=#<Bunny::Session:0x5110 [email protected]:5672, vhost=github-13521, addresses=[127.0.0.1:5672]> @open=true>
ch = c.create_channel
# => #<Bunny::Channel:14808 @id=2 @connection=#<Bunny::Session:0x5110 [email protected]:5672, vhost=github-13521, addresses=[127.0.0.1:5672]> @open=true>
qq = ch.quorum_queue("qq.1")
# => /path/to/bunny.git/lib/bunny/channel.rb:2078:in 'Bunny::Channel#raise_if_continuation_resulted_in_a_channel_error!': PRECONDITION_FAILED - cannot declare queue 'qq.1': queue limit in vhost 'github-13521' (4) is reached (Bunny::PreconditionFailed) @shaileshlaghane I have provided enough evidence that the feature does work as expected. |
Beta Was this translation helpful? Give feedback.
@shaileshlaghane this is not a bug report, this is an insult to open source software maintainers. If you cannot be bothered to even mention the set of steps to reproduce — which for this feature should be trivial — we won't bother to spend a second investigating.
In fact, we don't even have any details on the RabbitMQ version used.
This feature is known to work at scale at a number of RabbitMQ-as-a-Service environments, so without a way to reproduce against
4.0.7
all I can suggest is "you have the source, go solve your own problem".