Skip to Content

Version 27.1 by Thomas Mortagne on 2014/11/24
Show last authors
1 {{warning}}
2 This tutorial is a simple way to setup a XWiki clustering for test purpose. There is many ways to setup JGroups depending of your need.
3 {{/warning}}
4
5 {{toc/}}
6
7 The goal of a cluster of XWiki instance is to provide several XWiki in different servers accessing the same database server to be able to do load balancing.
8
9 = Install two instances of XWiki on the same MySQL database =
10
11 Here we will use the XWiki standard distribution but instead of using the embedded hsqldb database we will use a MySql database. For this you need to:
12
13 * modify the ##hibernate.cfg.xml## file to change hsqldb configuration by a proper MySQL configuration
14 * copy your database driver JAR in WEB-INF/lib or in some shared lib directory
15
16 See http://www.xwiki.org/xwiki/bin/view/AdminGuide/Installation for more details on how to install XWiki.
17
18 At this point you almost have a XWiki cluster: you have two instances of XWiki which are using the same datas. But there is a remaining "detail": the problem is that for performance reason XWiki is using lots of different caches which mean that even if one instance of XWiki modify a document it's possible the other XWiki instance will not see it and keep showing the document from its cache.
19
20 = Configure event distribution =
21
22 To handle this we will use the network event distribution system. When anything happens in a XWiki instances it generate a local event which is used to update caches. Here we will make theses events send to other XWiki instances as well and emulate local events. This way all the code updating its cache each time something changed in a particular document for example will also be notified if it has been done by another instance of XWiki.
23
24 == Enable remote observation ==
25
26 First you need to enable remote observation system.
27
28 For this go to xwiki.properties file and set the property ##observation.remote.enabled## to ##true##.
29
30 == Set the channels ==
31
32 Then you need to indicate to remote observation manager which communications channels it should start when XWiki starts.
33
34 For this you need to list in property ##observation.remote.channels## the names of the channels.
35
36 Here we set ##udp## in both instances to use embedded JGroups udp.xml configuration file which auto discover cluster members. In general you should always start by looking at the example configurations files in jgroups jar. Most of them are even configurable with system properties so you don't even have to copy and modify them.
37
38 = Start XWiki instance on different ports =
39
40 For this tutorial we run two instance of XWiki in the same server. So we need each instance to use different ports.
41
42 To run a XWik instance if a custom port you can provide it in parameter of the script start_xwiki.sh.
43
44 Here we start the first instance with:
45
46 {{code}}
47 sh start_xwiki.sh -p 8080 -sp 8070
48 {{/code}}
49
50 and the second one with:
51
52 {{code}}
53 sh start_xwiki.sh -p 8081 -sp 8071
54 {{/code}}
55
56 {{info}}
57 On XWiki versions < 6.2, you should use:
58
59 {{code}}
60 sh start_xwiki.sh 8080 8070
61 {{/code}}
62
63 and
64
65 {{code}}
66 sh start_xwiki.sh 8081 8071
67 {{/code}}
68 {{/info}}
69
70 The second port is the port used to stop jetty server, it's not mandatory to run XWiki but it's better to have differents ports if you don't want to have to kill the java process instead of using the stop_xwiki.sh script ;)
71
72 Sometimes you have to force the bind address, you can do it using ##-Djgroups.bind_addr=localhost##
73
74 = Check the clustering setup =
75
76 * Load a page in both instances
77 * Modify a page in one instance
78 * Reload it in the other instance
79 * It should have taken into account the modification made on the other instance
80
81 = Add load balancing with apache2 ##mod_proxy_balancer## =
82
83 You probably want to do load-balancing in front of the clustered XWiki instances. This section provides sample configurations to do that.
84
85 Replace if you have one your apache proxy configuration by the following one, or set it as proxy of your apache site configuration if you don't have one yet :
86
87 {{code language="apacheconf"}}
88 ProxyRequests Off
89 ProxyPreserveHost On
90
91 <Proxy balancer://mycluster>
92 BalancerMember ajp://127.0.0.1:8009 route=jvm1
93 BalancerMember ajp://127.0.0.1:9009 route=jvm2
94 ProxySet stickysession=JSESSIONID
95 </Proxy>
96 ProxyPass /xwiki balancer://mycluster/xwiki
97 {{/code}}
98
99 You need also to precise the name of the JVM route for each member of the balancer. On Tomcat, in ##conf/server.xml##, edit the ##Engine## node as follow :
100 {{code language="apacheconf"}} <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">{{/code}}
101
102 On GlassFish and Tomcat and probably others, you can set the system property jvmRoute to the same value.
103
104 Where you replace ##jvm1## by the name of the route you have precised in the Apache configuration.
105
106 This setting will complement the JSESSIONID with a suffix made by this jvmRoute: thus any session will contain the node name and this will instruct Apache to choose that route the next time a request comes. Thus, the browser will remain hooked to that server as long as the session remains.
107
108 == Testing the clustered setup ==
109
110 To test the load-balancing setup, you can edit the ##version.properties## file of your wiki to add a suffix to be able to recognize each member of the cluster. For example ##version=2.6.33077-node1## for the first node of a cluster of XWiki 2.6 nodes. Then, connect to the wiki via the URL that points to the load-balancer with a first browser, and look at which node is being used. Just after connect with a second browser (to have a different session), and make sure the node used is the other one (since mod_proxy_rewrite affects balancing members sequentially.
111
112 You can also verify the JSESSIONID cookie value which will end with the route name.
113
114 Finally, to test that clustering works you can either:
115
116 * set-up a dedicated virtual host to each cluster node so that you can check that, for example, a changed document, is changed on every node
117 * force the route by adding the URL parameter JSESSIOND=jvm1: this will make sure that this route is used which, in turn, will set the cookie to a session-identifier suffixed with jvm1.
118
119 = Monitoring and Troubleshooting =
120
121 The error log of Apache reports an amount of details about the choice of load-balancing if the log-level is sufficient.
122
123 The balancer-manager is also precious:
124
125 {{code language="apacheconf"}}
126 <Location /balancer-manager>
127 SetHandler balancer-manager
128 AuthType digest
129 AuthName "XWiki Cluster Management"
130 AuthType Digest
131 AuthDigestDomain http://example.com
132 AuthDigestFile /path/to/file.htdigest
133 Require valid-user
134 </Location>
135 {{/code}}
136
137 Using this configuration, properly specialized, provides a small interface at /balancer-manager where you can see the cluster nodes which are active, their load, and where you can disable them to take them offline for a bit.
138
139 == Debugging ==
140
141 See [[Debugging Section>>extensions:Extension.Observation Module Remote#HDebugging]] in the Observation Reference documentation.
142
143 You can also easily include the following HTML to force your browser to change from one node of the cluster to the other. This is extremely important to verify that clustering works:
144
145
146 {{code language="html"}}
147 <a href="$doc.name"
148 onclick="d = new Date(); d.setDate(d.getDate()+7); document.cookie='JSESSIONID=xxx.$hostname; ' + d.toUTCString()" ##
149 >$hostname</a>
150 {{/code}}
151
152 (where you replace $hostname (twice) and $doc.name appropriately.

About

About

Support

Platform

User Guide

Admin Guide

Developer Guide

Projects

XWiki

Extensions

Other

Contribute

Status

Practices

Under the Hood

Get Involved

Get Connected