By: marc caron user 31 Oct 2017 at 1:54 p.m. CDT

7 Responses
marc caron gravatar
I'm looking around and not seeing any documentation on how to "properly" upgrade a clustered setup. - Is it necessary to bring the whole thing down to upgrade the cluster? - Can (current version) keep running on the side nodes while the main node is upgraded? - Should all nodes (3 in our case) be brought down. Upgrade primary. Then setup the other 2 as "new" nodes with 3.1.1? - And any other options you can think of here. Thanks, recommended guidance on the flow would be nice for more than just me I think. I should add Assume staying with OpenDJ in this case. But it likely would be good to have info for when changing to OpenLDAP as well.

By Mohib Zico staff 31 Oct 2017 at 2:36 p.m. CDT

Mohib Zico gravatar
Hi Marc, Chris is going to introduce you with new cluster mechanism in 3.1.1 series. I am just giving some background info... Basically 2.4.4 cluster and 3.1.1 cluster are completely different and there is nothing like csync2 or other components clustering here in new 3.1.1 series. New cluster is more robust and you can manage clustering from GUI ( a cluster manager panel ). I think it's better for you to grab three new VMs and re-install new cluster. Single 2.4.4 upgrade is easy but clustered 2.4.4 is not unfortunately.

By marc caron user 31 Oct 2017 at 4:18 p.m. CDT

marc caron gravatar
Sounds good. I'll play with setting up a new 3.1.1 cluster. And then doing an upgrade of a single 2.4.4 to 3.1.1 then clustering it as that sounds like probably the smoothest option. Is there a different when using OpenDJ vs OpenLDAP for the clustering? The directions look to be for OpenLDAP and if it's easier to manage with one vs the other that would be my current leaning as our volume isn't anywhere near a scale to cause us issues either way.

By Chris Blanton staff 31 Oct 2017 at 4:41 p.m. CDT

Chris Blanton gravatar
Marc, We're going over the most viable solutions for you and should be able to update you ASAP. Of note is that fact that we've created a cluster management application that could ease configuring everything for you. We are looking in to how to tailor this to your specific needs. You can have a look at it if you like: [Cluster Manager]( Installation is simple, it just requires a small VM of Ubuntu 14 or 16, but can cluster Ubuntu or CentOS. Here's a video demonstration as well: [Installing Cluster Manager and Configuring a Cluster](

By Chris Blanton staff 03 Nov 2017 at 1:53 p.m. CDT

Chris Blanton gravatar
Marc, To upgrade your gluu from 2.4.4 to 3.1.1, you can follow these steps in [this documentation]( That being said, you must install 3.1.1 on other servers and use your former gluu server as an NGINX/Load balancing proxy, per [these instructions]( The logic behind that is having NGINX or some load-balancer/proxy to forward requests from 1 domain will allow you to access oxTrust/oxAuth on the other domains, due to certificate routing. It also allows failover if one of your nodes goes down, your other servers will be actively handling requests and authentications. So the process should go something like this: Follow the upgrade instructions until you have to install 3.1.1. Install 3.1.1 on a new server, then copy the backup data from you 2.4.4 server to the 3.1.1 server. Finish the upgrade instructions on the 3.1.1 server. After you've imported all your old data, follow the instructions from the manual clustering documentation for the rest of the nodes.

By Chris Blanton staff 03 Nov 2017 at 1:56 p.m. CDT

Chris Blanton gravatar
Another thing to ease your installation of a cluster is using Cluster Manager after you've upgraded the 3.1.1 server, and use it to cluster the rest for you.

By marc caron user 06 Nov 2017 at 10:21 a.m. CST

marc caron gravatar
Thanks. I'll close this ticket for now while working through this as I'm sure it'll take some trial and error on my part.

By Chris Blanton staff 06 Nov 2017 at 10:23 a.m. CST

Chris Blanton gravatar
Marc, If you need any help, let use know.