[rabbitmq-discuss] RabbitMQ 1.5.0 released

Fri Dec 19 10:51:45 GMT 2008

On Fri, Dec 19, 2008 at 8:11 AM, Ben Hood <0x6e6562 at gmail.com> wrote:

> > 2) What would be the right way of upgrading rabbitmq on a running server
> > without shutting it down? (I know erlang supports this feature but I
> failed
> > to find something about it in the documentation).
>
> This is supported in Erlang and I use it a lot myself when hacking on
> Rabbit but we are not yet making use of it from a release perspective.
> One of the issues that you would run into (which is not necessarily
> Erlang specific) is dealing with schema upgrades in mnesia, i.e. you
> would have to migrate the database (which changed considerably between
> 1.4 and 1.5). I should imagine that as Rabbit matures more, we could
> make more use of this feature.
>
> Having said that, I know that Edwin is using OTP release handling with
> Rabbit, whereas the official Rabbit release management is more OS
> package manager centric, so he may be able to comment on this.

So, what would be my course of upgrade in a running server? Stop rabbit,
upgrade and start it again and it should upgrade the mnesia-db?

>
>
> http://hopper.squarespace.com/blog/2008/11/9/flow-control-in-rabbitmq.html
>

>
> "From a protocol perspective, when the broker decides that it is
> running out of resources to buffer an imbalance, it sends a
> channel.flow command out to every channel. This command contains a
> flag to indicate to a client whether content bearing AMQP methods can
> be sent or not. So if a client receives this command with the flag set
> to false, then the client should suspend sending any further content
> bearing methods (e.g. basic.publish), until such a time that the
> broker notifies the client that it is safe to resume. The notification
> of resumption is the opposite of the pause - the broker sends a
> channel.flow command with the flag set to true."
>
>
Thanks for the info and the link. I'll read more about it.

Eran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20081219/2b291b0a/attachment.htm 