[rabbitmq-discuss] Redefining queue/exchange attributes

Sat Apr 21 17:01:44 BST 2012

>
> However, we're more likely to go in the direction of having things like
> HA-ness defined outside of the AMQP arguments mechanism altogether in future

> The application should not have to know that its queues are HA or its
> exchanges are federated; that's a matter for the broker administrator

Great to hear that you've got that in mind, Simon! It would improve
things immeasurably for both application code, broker management,
and coincidentally is my biggest gripe with the current state of RabbitMQ
HA. Would love to see work in that direction sometime in the future.

- Brendan

On Fri, Apr 20, 2012 at 6:56 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> We're aware that the current situation with HA policies is inconvenient;
> it was the simplest thing that could possibly work.
>
> However, we're more likely to go in the direction of having things like
> HA-ness defined outside of the AMQP arguments mechanism altogether in
> future. Really arguments should be for things that application authors care
> about; it's a contract with the application that these should not change.
> The application should not have to know that its queues are HA or its
> exchanges are federated; that's a matter for the broker administrator.
>
> Cheers, Simon
>
>
> On 20/04/12 17:51, Elias Levy wrote:
>
>> Are there any plans to allow the modification of queue and exchange
>> attributes, say via the REST API?
>>
>> At the moment if one must redefine the attributes of a queue or
>> exchange, you must destroy the queue or exchange and recreate it.  That
>> is rather disruptive in a production environment.  If means that
>> bindings are destroyed and must be recreated, that consumers must
>> restart their subscriptions, etc.
>>
>> There are many scenarios where one would want to redefine the
>> attributes.  Either an error crept in during initial set up, or say, a
>> node has gone down and you want to redefine a HA queue by removing the
>> dead node from its config and adding a new node.
>>
>> Thoughts?
>>
>> Elias Levy
>>
>>
>>
>> ______________________________**_________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
>> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>>
>
>
> --
> Simon MacMullen
> RabbitMQ, VMware
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120421/6699dbbd/attachment.htm>