Confluence 4.0 : Confluence Cluster Installation
This page last changed on Sep 15, 2011 by edawson.
OverviewThere are two methods of installing Confluence in a cluster, depending on whether you have existing data. This page describes a fresh installation with no existing data. See also Confluence Cluster Installation with Existing Data.
Installation with no existing dataTo get Confluence running in a two-node cluster, you must do the following:
Each of these steps will be described in detail below. 1. Clustering requirementsYour Confluence cluster installation must meet all the following criteria for clustering:
Clustered commercial licenses may be purchased through Confluence website. Clustered evaluation licenses may be obtained by emailing sales@atlassian.com. A cluster can run using two copies of Confluence Standalone. However, cluster administrators must understand how to configure an application server and web server with load balancing, so we recommend you are comfortable installing Confluence as a EAR/WAR in your application server before proceeding with a clustered installation. 2. Installation on first nodeCluster administrators should already be comfortable with the normal installation method, so it won't be repeated here. There are two differences in the Confluence Setup Wizard from a normal installation:
3. Load test the single nodeMost Confluence installations do not need to be clustered. Ensure you have tested your single node installation with the number of users you expect to host before going ahead with the additional complexity of clustering. Check out our performance tuning tips for ways to improve the performance of a single instance of Confluence. You can upgrade your single node to a multi-node cluster at any time by resuming this guide from step 4 below. 4. Copy Confluence to second nodeConfluence clusters must use the same JDK, application server and application. The easiest way to ensure this is to shut down Confluence on the first node, then copy its web application and home directory to the second node:
Copying the web application ensures any modifications you have made to the application itself, custom LDAP settings ( Copying the home directory ensures the Confluence search index (the 5. Start Confluence on the first node, wait, then start Confluence on second nodeFor the most stable start-up process, it is important to start Confluence one server at a time.
6. Test cluster connectivityThe Cluster Administration page (Administration, Cluster Configuration) includes information about the active cluster. When the cluster is running properly, this page displays:
A simple process to ensure your cluster is working correctly is:
7. Configure load balancerFor the moment, configuring the load balancer is outside the scope of this document. However, a simple Apache and Tomcat load-balancing configuration is available, which includes sample configuration for the Apache Tomcat and the Apache web server, using its load-balancing JK connector. TroubleshootingIf you have problems with the above procedure, please see our Cluster Troubleshooting guide. Upgrading a clusterIt is important that upgrades follow the procedure for Upgrading a Confluence Cluster. Related documentationOverview of Confluence Clusters |
![]() |
Document generated by Confluence on Sep 19, 2011 02:48 |