Changes for page Clustering

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -16,11 +16,13 @@
16	16
17	17	XWiki stores a lot of information in Solr cores (e.g. Events, Indexed content), so like with the database you will need to make sure that all cluster members use the [[same Solr instance remotely>>extensions:Extension.Solr Search API#HSetuparemoteSolrserver]] instead of each having its own embedded instance.
18	18
19		-== Enable event distribution ==
	19	+== Event distribution
20	20
	21	+=== Enable event distribution ===
	22	+
21	21	To enable event distribution in an XWiki instance go to ##xwiki.properties## file and set the property ##observation.remote.enabled## to ##true##.
22	22
23		-== Setup communication channels ==
	25	+=== Setup communication channels ===
24	24
25	25	You will need a configuration file for each different cluster group you want to setup. Generally there is only one for a simple cluster.
26	26
...	...	@@ -29,7 +29,7 @@
29	29	* use one of the files provided by jgroups ("tcp", "udp", etc. it's generally enough for most use cases and certainly a lot simpler) which can be customized through system properties
30	30	* create your own configuration file
31	31
32		-=== Create your own configuration file ===
	34	+==== Create your own configuration file ====
33	33
34	34	For this go to the ##/WEB-INF/observation/remote/jgroups## folder and add one xml file.
35	35
...	...	@@ -37,19 +37,19 @@
37	37
38	38	If you have IPv6 on your server, you are also advised to read [[this IPv6 article>>https://community.jboss.org/wiki/IPv6]]. Defining ##-Djava.net.preferIPv4Stack=true## when launching the JVM is probably your best bet in most cases. If your really want to use IPv6 for your channels, you should probably upgrade JGroup to version 2.10.0.GA and use a JVM 6 at least.
39	39
40		-== Start communication channels ==
	42	+=== Start communication channels ===
41	41
42	42	The name of the xml file matches the identifier of the channel.
43	43
44	44	To indicate which channels to start when XWiki starts list them in the property ##observation.remote.channels## of the ##xwiki.properties## file.
45	45
46		-== Choose network adaptor implementation to use ==
	48	+=== Choose network adaptor implementation to use ===
47	47
48	48	By default only JGroups implementation is provided, but it's possible to add more. See the [[Remote Observation Module>>extensions:Extension.Observation Module Remote#HAddcustomnetworkadaptor]] for more details.
49	49
50	50	== Shared filesystem ==
51	51
52		-Attachments and deleted documents located on the file system (located inside the [[Permanent Directory>>Documentation.AdminGuide.Configuration.WebHome#HPermanentDirectory]]) are not clustered and in order for all XWiki instance to access and display them properly in the UI, you'll need to set up a shared filesystem (e.g. NFS) and share the ##store/file## directory.
	54	+Attachments and deleted documents located on the file system (located inside the [[Permanent Directory>>Documentation.AdminGuide.Configuration.WebHome#HPermanentDirectory]]) are not clustered and in order for all XWiki instance to access and display them properly in the UI, you'll need to set up a shared filesystem (e.g. NFS) and share the ##store/file## directory.
53	53
54	54	Note that you must not share the whole Permanent Directory or this will lead to problems (such as causing file contentions when several instances try to read/write to some of them which have locks on).
55	55
...	...	@@ -57,10 +57,10 @@
57	57
58	58	The following limitations currently exist when you use clustering:
59	59
	62	+* [[XWIKI-21548>>https://jira.xwiki.org/browse/XWIKI-21548]]: Realtime editing currently doesn't work on a cluster. Each node will create a different realtime session, and the collaboration will be with the users that end up on the same cluster node.
60	60	* [[XWIKI-6235>>https://jira.xwiki.org/browse/XWIKI-6235]]: The Scheduler feature is not cluster-aware and thus each node of XWiki runs its own scheduler and thus the same scheduler jobs will execute on all nodes. The workaround is to disable the Scheduler plugin on all nodes except on one (i.e remove ##com.xpn.xwiki.plugin.scheduler.SchedulerPlugin## from the ##xwiki.plugins## configuration value in ##xwiki.cfg##). Note that this creates a [[SPOF>>https://en.wikipedia.org/wiki/Single_point_of_failure]] and if the node containing the active Scheduler is down, the scheduled jobs won't execute.
61		-* [[XWIKI-14722>>https://jira.xwiki.org/browse/XWIKI-14722]] & [[XWIKI-1516>>https://jira.xwiki.org/browse/XWIKI-15164]]: Attachments and deleted documents located on the file system (located inside the [[Permanent Directory>>Documentation.AdminGuide.Configuration.WebHome#HPermanentDirectory]]) are currently not clustered. See above on setting up a shared filesystem to work around this.
62	62	* [[XWIKI-11441>>https://jira.xwiki.org/browse/XWIKI-11441]] If a node is down and Events happen, these Events won't be propagated to the node when it comes back up. For example, imagine you install an Extension on a node of the cluster while another node is down. When that node is restarted, the Extension won't be installed on it.
63		-* [[XWIKI-21548>>https://jira.xwiki.org/browse/XWIKI-21548]]: Realtime editing currently doesn't work on a cluster. Each node will create a different realtime session, and the collaboration will be with the users that end up on the same cluster node.
	65	+* [[XWIKI-14722>>https://jira.xwiki.org/browse/XWIKI-14722]] & [[XWIKI-1516>>https://jira.xwiki.org/browse/XWIKI-15164]]: Attachments and deleted documents located on the file system (located inside the [[Permanent Directory>>Documentation.AdminGuide.Configuration.WebHome#HPermanentDirectory]]) are currently not clustered. See above on setting up a shared filesystem to work around this.
64	64
65	65	= Performances =
66	66