[Operators] Ejabberd upgrades and mnesia multinode setup

Peter Saint-Andre peter at andyet.net
Thu Aug 6 01:51:29 UTC 2015


Modded

Sent from mobile, might be terse 

> On Aug 5, 2015, at 5:25 PM, Mr. Glen J. Loftin <glenloftin at loftintechnologies.com> wrote:
> 
> What do you all know about x-ass 
> 
> Sent from my iPhone
> 
> On Aug 3, 2015, at 10:26 AM, Mickaël Rémond <mremond at process-one.net> wrote:
> 
>> Hello Holger,
>> 
>> Holger Baust said:
>> 
>> Hi!
>> 
>> I am planning to upgrade jabber.freenet.de soon.
>> But this is a multinode setup with 2 nodes.
>> 
>> Has anyone done this yet and can give me some advises?
>> (only ejabberd specific please)
>> 
>> Since these Nodes run as Virtual Machines on VMWare clusters,
>> I have the advantage of using snapshot for roll-backs.
>> 
>> It should be quite a straightforward operation.
>> 
>> My advice are the following:
>> 
>> Backup Mnesia DB and relational backend.
>> Take a snapshot of your VM for rollbacks.
>> Assess if you can migrate one node at a time. If you can simulate cluster update on snapshot outside of the production context it would be good. Depending on which version you are and which version you are getting two, it may be possible to mix cluster nodes from two versions (if internal data structure between the two versions did not change)
>> Shutdown nodes (or only one if possible) and upgrade code, but keep data and restart the nodes in reverse order (otherwise, the service will wait for the latest online master to go up to really start).
>> Does it make sense ? Do you have more specific questions ?
>> 
>> -- 
>> Mickaël Rémond
>> http://www.process-one.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/operators/attachments/20150805/7c0eb4c4/attachment.html>


More information about the Operators mailing list