[rabbitmq-discuss] Fwd: Recovery and Upgrade Path
alexis.richardson at gmail.com
Fri Jun 5 20:09:29 BST 2009
With Estaban's permission, I am forwarding this to the list.
Estaban I think your own suggestion is reasonable but you could also
look at our Windows service for that platform.
Re Erlang, think of it as being like Java. You won't upgrade it very
often. Read the RabbitMQ release notes for upgrade recommendations.
---------- Forwarded message ----------
From: Steve Weaver <weaveinator at gmail.com>
Date: Fri, Jun 5, 2009 at 4:37 AM
Subject: Re: [rabbitmq-discuss] Recovery and Upgrade Path
To: Alexis Richardson <alexis.richardson at gmail.com>
Hi Alexis -
Thanks for the reply. So yeah I was wondering if I just create a bat
file (and shell script) on Windows Server/RHE server so if the box
ever crashes or gets a reboot that RabbitMQ will come back
automatically. That is what I was thinking but wanted to know if that
was the best way.
Next is - yes - what is the best (and read easiest) way to upgrade and
I'm thinking to remove the old version completely and reinstall. But
the reason why I ask is - on Red Hat - do I need to upgrade Erlang
first? Its included in the Windows install so no worries there.
Thanks so much for your help - and sorry if I sound like I'm new. Its
only because I am.
On Thu, Jun 4, 2009 at 5:29 AM, Alexis Richardson
<alexis.richardson at gmail.com> wrote:
> Hey there.
> On Mon, Jun 1, 2009 at 1:04 AM, Steve Weaver <weaveinator at gmail.com> wrote:
> > Hi all -
> > Have a two part question on RabbitMq. First I have RabbitMq running on both
> > Windows Server and RHE server and was wondering what is the best way to go
> > about recovery if the server itself fails or RabbitMq needs a restart. I'm
> > messing around with creating a windows service that starts it for the
> > windows box but was wondering what the best practice is for both windows and
> > linux.
> RabbitMQ can already run as a Windows service; if you want to use that
> to manage restarts, then that seems perfectly reaosnable to me.
> I would not go so far as to say there is 'best practice' in these
> cases. How often might you need to restart and why? Do you need to
> recover data from disk? Will you be running a cluster or just one
> node? How much automation do you need?
> Let folks know, and some people might have some war stories and
> recommendations that help ;-)
> > Next - we are talking about upgrading rabbitmq so is that a just a matter of
> > unistalling/reinstalling or can I just rebuild over the top of the older
> > version. I'm thinking more the point is for the RHE server as I'm still
> > getting the hang of the command line stuff (linux noob for the most part) so
> > that may just be clearing out the directory and dropping / compiling the new
> > version there.
> Are you asking: "how can I migrate my old configuration to a new install"?
> > Thanks very much for any help or insight!
> > Estaban
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
More information about the rabbitmq-discuss