This page last changed on Sep 15, 2011 by edawson.
 | Please be aware that Confluence clustered is not available for version 4.0 yet. It will be forthcoming in a minor release of Confluence following the release of version 4.0.
|
OverviewThere are two methods of installing Confluence in a cluster, depending on whether you have existing data. This page describes how to upgrade an existing Confluence instance into a cluster. See also Cluster installation without existing data.  | Oracle Coherence Licensing Change:
- Due to a license agreement change,Confluence is now available in two editions:
- Standard Edition — Confluence with Ehcache's caching technology (available to customers with non-clustered Confluence licenses).
If you are currently running a clustered installation of Confluence, please do not upgrade it with a standard edition of Confluence.
- Clustered Edition — Confluence with Oracle's Coherence clustering and distributed caching technology (available to customers with Confluence clustered licenses only).
- For more information about these changes, please refer to the Coherence License Changes document.
- If you have a Confluence clustered license, are running a clustered installation of Confluence and wish to upgrade to Confluence version 2.6 or later, please ensure that you download only a clustered edition of Confluence and please refer to the Confluence 3.0.1 Upgrade Notes for additional upgrade information.
|
Cluster installation from an existing copy of ConfluenceBEFORE ATTEMPTING THIS, PLEASE MAKE A BACKUP. To upgrade an existing copy of Confluence to run in a two-node cluster, you must do the following: - Ensure that your standalone version of Confluence has been upgraded to the version you want to run the Cluster on. Do not upgrade your version of Confluence and switch to the clustered version at the same time. First upgrade your system (e.g. from Confluence 2.5.8 Standalone to 2.7.1 Standalone) and make sure everything works fine (e.g. for a week) before switching (e.g. from Confluence 2.7.1 Standalone to 2.7.1 Clustered)
- Ensure you meet the clustering requirements, including obtaining a clustered license key from Atlassian for each node
- Due to CONF-8959, you need to perform attachment migration to the database before you change your license to a clustered license
- Upgrade the existing Confluence instance to a clustered license. Do this by going to Admin> Licence Details. Confluence should warn you that this version of Confluence is not capable of clustering.
- Shutdown Confluence. Deploy a clustered version of Confluence (Do not attempt to install any version of Confluence that is not the Clustered equivalent to your current release). Edit confluence-init.properties (confluence-ver-clustered/confluence/WEB-INF/classes/confluence-init.properties) to set confluence.home to the same path as the old home. Start the first node, and verify that things are working correctly.
- Shut down the first node, copy the Confluence application and Confluence home directory to the second node
- Start the first node, wait until it is running, then bring up the second node and it will automatically join the cluster
- Test the cluster is working correctly
- Configure a load balancer in front of the two clustered nodes.
Each of these steps will be described in detail below. 1. Clustering requirementsYour Confluence cluster installation must meet all the following criteria for clustering: - you must be running Confluence 2.3 or later
- you must have a clustered license
- you must use an external database
- you must use a load balancer with session affinity in front of the cluster.
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. You can follow the instructions to Migrate Confluence to an external database. 2. Upgrade existing instance to clustered licenseOnce you've obtained your clustered license from Atlassian, you can simply update the license in your running Confluence instance: - Go to 'Administration'.
- Go to 'License Details', and paste in the new license.
- Click 'Save'.
When you enter a clustered license, you will see a new line appear on this page: Licensed Clustered Nodes. This tells you how many nodes your Confluence license will allow.  License Details page shows the number of cluster nodes permitted
3. Migrate your attachments to the DatabaseYou can do this by navigating to Admin> Attachment Storage > Edit, and changing it to "Database". 4. Copy Confluence to second nodeFor the remaining steps in setting up a cluster with existing data, please continue from step 4 in the normal Confluence cluster installation guide. 5. Start Confluence on the first node, wait, then start Confluence on second nodeSee comment in step 4. 6. Test cluster connectivitySee comment in step 4. See comment in step 4. 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. Overview of Confluence Clusters Confluence Cluster Installation Confluence Installation Guide Upgrading a Confluence Cluster Confluence User Guide
|